| 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, I'm facing a problem:
I have a global entity that contains several childs:
global entity: PABX
|
child entities: PABX_ALARM (dynamic=false)
|
----------------------------------------
| | | |
ALARM_INPUT ALARM_OUTPUT ALARM_GROUP ALARM_CLASS
(dynamic = (dynamic = (dynamic = (dynamic =
true) true) true) true)
I want to register the PABX and the PABX_ALARM.
The IDENTIFIER of PABX is: - Pabx Name
The IDENTIFIER of PABX_ALARM is: - Alarm Board Position
From the SRM I understood that it is not allowed to assign a DNS_IDENT to a
child entity class.
I know the procedure to register an global entity (without children (and with
dynamic children only -> shown structure with PABX_ALARM omitted) ):
- add reference attributes
- add register directives (register, deregister, directory etc)
- add show identifiers entry-point
for the global entity.
What procedure is needed to register the static child entity PABX_ALARM ?
- add reference attributes for the child ?
- add register directives for the child ?
- add show identifiers entry-point ?
- datatype of identifier of child ?
- what DNS_IDENT for child (this is not allowed !) ?
Can someone answer these questions or has an example of how to do it ???
My thanks will be great !
Regards Paul
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1468.1 | Some (quick) answers... | CHRISB::BRIENEN | DECmcc Bridge|Station|SNMP Management. | Tue Sep 10 1991 09:43 | 27 |
>What procedure is needed to register the static child entity PABX_ALARM ? > - add reference attributes for the child ? No, This is not required, but can optionally be done (in the .MS file, not in the AM's code: REFERENCE partition is handled by REGISTRATION FM). > - add register directives for the child ? YES, this is required (add REGISTER directive to .MS file). > - add show identifiers entry-point ? Yes, This is required. Make sure that wildcard is supported for PABX_ALARM (even if just one instance exists: I believe Registration FM will do a SHOW IDENT using wildcard for children with DYNAMIC = FALSE). > - datatype of identifier of child ? I'm not aware of any current limitations. Bridge AM, for example, uses datatypes like Unsigned8, ID802, ENETV2_TYPE, and NULL for Child identifier datatypes (and they all REGISTER just fine). > - what DNS_IDENT for child (this is not allowed !) ? Don't bother to specify this... Chris | |||||
| 1468.2 | naming uniqueness | TOOK::CALLANDER | Jill Callander DTN 226-5316 | Wed Sep 11 1991 10:27 | 12 |
I am not sure if the names you used in .0 were the names you were hoping to register, if so you will have a problem with the global attribute pabx name coming in conflict with the child entity name of pabx_... I believe the registry program will call that out as a conflict since pabx will not be unique. In reality it will parse because the parser stores the entity class names in a seperate tabel from the attribute names, but you will NEVER be able to get at the pabx name attribute from the command line since it will always be seen as the pabx_... child entity (instance value ="name"). jill | |||||