| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hi,
We are trying to find a way to easily do a directory of a
domain and underlying tree structure in order to find out what nodes
exist and in what domains. We found the following to commands that
work recursively:
directory node4 *, in domain = "domain name"
show node4 * all attributes, in domain = "domain name"
But neither tell us in what domain it found the node4 in.
Example:
directory node4 *, in domain = .eu.by.byl.b151
Node4 DECNOS_NS:.eu.by.byl.bylv21_2
AT 8-APR-1992 16:24:00
Directory successful.
Registered Name = DECNOS_NS:.eu.by.byl.bylv21_2
Address = 1.82
Name = BYLV21
Node4 DECNOS_NS:.EU.BY.BYL.BYLV07
AT 8-APR-1992 16:24:05
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLV07
Address = 1.68
Name = BYLV07
Node4 DECNOS_NS:.EU.BY.BYL.BYLV08
AT 8-APR-1992 16:24:06
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLV08
Address = 1.108
Name = BYLV08
Node4 DECNOS_NS:.EU.BY.BYL.BYLV06
AT 8-APR-1992 16:24:07
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLV06
Address = 1.65
Name = BYLV06
Node4 DECNOS_NS:.EU.BY.BYL.BYLV05
AT 8-APR-1992 16:24:08
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLV05
Address = 1.60
Name = BYLV05
Node4 DECNOS_NS:.EU.BY.BYL.BYLV01
AT 8-APR-1992 16:24:09
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLV01
Address = 1.5
Name = BYLV01
Node4 DECNOS_NS:.EU.BY.BYL.BYLP01
AT 8-APR-1992 16:24:15
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLP01
Address = 1.8
Name = BYLP01
Node4 DECNOS_NS:.EU.BY.BYL.BYLV26
AT 8-APR-1992 16:24:16
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLV26
Address = 1.123
Name = BYLV26
Node4 DECNOS_NS:.EU.BY.BYL.BYLA02
AT 8-APR-1992 16:24:17
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLA02
Address = 1.90
Name = BYLA02
Node4 DECNOS_NS:.EU.BY.BYL.BYLU08
AT 8-APR-1992 16:24:22
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLU08
Name = BYLU08
Address = 1.396
Node4 DECNOS_NS:.eu.by.byl.byls57
AT 8-APR-1992 16:24:24
Directory successful.
Registered Name = DECNOS_NS:.eu.by.byl.byls57
Address = 1.398
Name = byls57
Node4 DECNOS_NS:.EU.BY.BYL.BYLS24
AT 8-APR-1992 16:24:25
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLS24
Address = 1.162
Name = BYLS24
Node4 DECNOS_NS:.EU.BY.BYL.BYLS06
AT 8-APR-1992 16:24:26
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLS06
Address = 1.6
Name = BYLS06
Node4 DECNOS_NS:.EU.BY.BYL.BYLS36
AT 8-APR-1992 16:24:28
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLS36
Address = 1.291
Name = BYLS36
Node4 DECNOS_NS:.EU.BY.BYL.BYLS23
AT 8-APR-1992 16:24:30
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLS23
Address = 1.161
Name = BYLS23
Node4 DECNOS_NS:.EU.BY.BYL.BYLS42
AT 8-APR-1992 16:24:31
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLS42
Address = 1.303
Name = BYLS42
Node4 DECNOS_NS:.EU.BY.BYL.BYLW18
AT 8-APR-1992 16:24:34
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLW18
Address = 1.574
Name = BYLW18
Node4 DECNOS_NS:.EU.BY.BYL.BYLG03
AT 8-APR-1992 16:24:42
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLG03
Address = 1.452
Name = BYLG03
Node4 DECNOS_NS:.EU.BY.BYL.BYLG01
AT 8-APR-1992 16:24:44
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLG01
Address = 1.24
Name = BYLG01
Node4 DECNOS_NS:.EU.BY.BYL.BYLR05
AT 8-APR-1992 16:24:45
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLR05
Address = 1.142
Name = BYLR05
Node4 DECNOS_NS:.EU.BY.BYL.BYLR01
AT 8-APR-1992 16:24:47
Directory successful.
Registered Name = DECNOS_NS:.EU.BY.BYL.BYLR01
Address = 1.453
Name = BYLR01
We know that for example .eu.by.byl.bylr01 is in the domain .eu.by.byl.b151_rr,
but the listing does not tell us that. The show command doesn't tell us
either. Is there another command, or form of the directory and/or show
command that will tell us this info. Somehow DECmcc must know, because it
found all the node4's in the underlying domains.
Thanks,
Julie Ann
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2740.1 | A procedure will do it | TOOK::R_SPENCE | Nets don't fail me now... | Thu Apr 16 1992 14:19 | 25 |
You can show members of a domain and you can show all domains.
The tool
NETS::USER$NETS:MCC_DUMP_DNS.COM
can be used to get a list of all that is in your domains.
You use it like;
@mcc_dump_dns * DOMAIN
and it will creat a procedure that could be used to recreate al
domains and members.
You supply a global entity class for P2 and it extracts all
instances of that class.
Currently P1 (which I hoped to make it just do a single domain) isn't
working so if you need to specify P2, you must supply an asterisk
for P1.
I hope this helps.
By the way, if you look at what the code does you can see how to
get what you need.
s/rob
| |||||
| 2740.2 | check your definition of USER$NETS | MCDOUG::MCPHERSON | Save a tree: kill an ISO working group. | Thu Apr 16 1992 14:27 | 24 |
$ cop NETS::USER$NETS:MCC_DUMP_DNS.COM mcc_common:*.* %COPY-E-OPENIN, error opening NETS::USER$NETS:MCC_DUMP_DNS.COM; as input -RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file $ $ dir NETS::USER$NETS:MCC_*.com %DIRECT-E-OPENIN, error opening NETS::USER$NETS:MCC_*.COM;* as input -RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file $ $ dir NETS::USER$NETS: %DIRECT-E-OPENIN, error opening NETS::USER$NETS:*.*;* as input -RMS-E-DNF, directory not found -SYSTEM-W-NOSUCHFILE, no such file $ | |||||
| 2740.3 | not exactly what I had in mind | COL01::LUNT | Thu Apr 16 1992 17:38 | 12 | |
Thanks for the answer, but I was really looking for a nice simple
DECmcc directive that would do this for me. The directory directive
that I illustrated in my note would be perfect if the parental domain
name was also printed out. DECmcc must have this information if it is
able to print all node4 entities in the current and all subdomains. Why
doesn't it print it out? I also have command procedures that can give
me this info, but my customer would like to have a DECmcc directive. To
have to keep telling them, oh we can just write a command procedure
to do that is getting really old.
Julie Ann
| |||||
| 2740.4 | Maybe in the next release... | MCDOUG::MCPHERSON | Save a tree: kill an ISO working group. | Thu Apr 16 1992 18:01 | 6 |
> Thanks for the answer, but I was really looking for a nice simple > DECmcc directive that would do this for me. The directory directive Such a directive doesn't exist. You're right, though: it would be nice. /doug | |||||
| 2740.5 | Simple | TOOK::R_SPENCE | Nets don't fail me now... | Fri May 01 1992 16:08 | 5 |
MCC> show domain * member *
should do it
s/rob
| |||||
| 2740.6 | Corection for .1 | TOOK::R_SPENCE | Nets don't fail me now... | Fri May 01 1992 16:10 | 7 |
re; .1
Ooops, I blew it on the directory spec (I left it out);
NETS::USER$NETS:[MCC011.S-KIT]MCC_DUMP_DNS.COM
s/rob
| |||||
| 2740.7 | Finding what domain an entity belongs to. | TOOK::A_MOORE | Fri May 01 1992 19:44 | 13 | |
Finding what domain an entity belongs too command. This is good suggestion. I see possible solutions. The iconic map could add a nice window that would return all the domains that an entity belonged to. The Domain FN has a member assocation directive available from a program. Member assocation unfortunately will not parse and be supported by FCL. Another possiblity is to make hidden enumerate verb supported. And the orginal suggestion also is possible. So Help us set the correct customer value and prority for this new feature. We need to deliver what the customer wants most first. Al Moore | |||||
| 2740.8 | priority high | COL01::LUNT | Mon Jul 06 1992 12:34 | 21 | |
Hi,
I think this is just one of many tools that NEED to be built into
DECmcc. Time saving features such as being able to update your
DECmcc database (domain directory, address) are also very high on
my list, but I would say a "find" command is higher. We have over 1200
domains. When I am troubleshooting a problem, the Iconic map
doesn"t come into question, because I can't find the icons. But then
I also loose the best feature of the iconic map: Toplogy
documentation. When I use the FCL, I still haven"t an idea where the
node is located, which may be critical to know. I think you get the point.
How can we help to prioritize this request and other features? I
keep hearing about a "grand list" of requests that will be prioritized
and then funded based on this list.
Is there anyway that this list can be made internally public?
Thanks,
Julie Ann
| |||||