[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

3767.0. "members of entire hierarchy" by CTHQ::WOODCOCK () Fri Sep 18 1992 10:18

Hi there,

I'm looking to determine all entities within a domain hierarchy by using a
little routine. I was *real* pleased to see the output of the following command
SHOW DOMAIN *,IN DOMAIN .BLAH produce what looks like all the domains in the
domain hierarchy. Are there any limitations to be aware of? That is, does it
find all domains within the ENTIRE structure or does it just go down a level
or two? Also the DIRECTORY command seems to produce the same output, are there
any differences at all (output or performance to get data)?

To carry all this one step further is there any way of determining the actual
entities within the entire hierarchy thru similar commands which would 
propagate down thru the domains??

many thanks for any help!
brad...
T.RTitleUserPersonal
Name		DateLines
3767.1No Limits.TOOK::A_MOOREFri Sep 18 1992 12:4421
Hi Brad,

There isnt any practical limit.  Stacksize might go before diskspace in the end.
Some where else in the system there is domain depth limit which I do not recall.

There is one feature to be aware of.  It only expands dynamic domains.  It does 
look into or list the contents of static domains.  When created dynamic domains 
must be in a hierarchy.  There are no rules for static domains, put them anywhere. 

To list all the node4s in a domain hierarchy do a:

	Directory NODE4 * , in domain foo

I am sure what your goal is here, but in V1.3.1 there is a new feature that might
help.   It is Cross Domain Membership Search.  It is involked from the applications 
menu. You enter an entity identifier,  Toggle the class, and a list of domains is
presented.  Click on one of the domains listed and that map is opened. It works 
now.  So if a call comes in, the operator can easily open the correct map to 
manage it.

Al
3767.2a routine is neededCTHQ::WOODCOCKFri Sep 18 1992 15:0528
Hi Al,

Good info for limits and domain type.

>I am sure what your goal is here, but in V1.3.1 there is a new feature that might
>help.   It is Cross Domain Membership Search.  It is involked from the applications 
>menu. You enter an entity identifier,  Toggle the class, and a list of domains is
>presented.  Click on one of the domains listed and that map is opened. It works 
>now.  So if a call comes in, the operator can easily open the correct map to 
>manage it.

Actually I'm looking for a text listing of EVERYTHING (including class) in any 
given domain structure to be used by other procedures. I was hoping there was
a magic potion I could call on to get this info. I guess I'll need a
routine to do the following: 

dir domain *,in domain TOP 	!gets listing of all domains
show domain A member *     	!one of these for each domain in list

Getting the class info is another story. The only way to do this is to execute
the command you described DIR NODE4 *,in domain A. But I need a command for
each CLASS for each domain. This was something I wanted to avoid. Fortunately
I only need to know the CLASS info for a subset of entities. This whole subset
will be placed into a seperate domain so I'll only need one command for each
class.

thanks,
brad...