| 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 |
Using the FCL PM and NO domain qualifiers:
I have a CREATE <global-entity> entry point that creates the actual object.
In addition , This CREATE does the following:
1. If the object exists in DNS (has been previously registered), it
adds some entity-specific attributes to the DNS object.
2. If the object does not exist in DNS, it creates the object in DNS
and then adds the specific attributes.
Now, if I submit these directives in the following ORDER:
REGISTER ENTITY .dns-dir.obj-name
CREATE ENTITY .dns-dir.obj-name {arg=value...}
DIRECTORY ENTITY .dns-dir.obj-name
DIRECTORY ENTITY .dns-dir.* ! all objects in the DNS directory
everything works and this last command finds the object (and others).
If I reverse the order of the first two commands:
CREATE ENTITY .dns-dir.obj-name {arg=value...}
REGISTER ENTITY .dns-dir.obj-name
then
DIRECTORY ENTITY .dns-dir.obj-name
DO find the object while
DIRECTORY ENTITY .dns-dir.*
DOES NOT find any object and returns with a no entity exception:
No such entity: QMS_REPOSITORY TPEDNS_NS:.repository.*
Unknown Entity = QMS_REPOSITORY
TPEDNS_NS:.repository.*
Is there an explanation or is it a problem ?
Thanks,
Phil
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1525.1 | exi | TOOK::JESURAJ | Mon Oct 14 1991 15:14 | 18 | |
>I have a CREATE <global-entity> entry point that creates the actual object.
>
>In addition , This CREATE does the following:
> 1. If the object exists in DNS (has been previously registered), it
> adds some entity-specific attributes to the DNS object.
> 2. If the object does not exist in DNS, it creates the object in DNS
> and then adds the specific attributes.
^^^^^^^^^^^^^^^^^^^^^^^^^^^
Can you give us these attributes? Possibly there is a
conflict among the ID codes and hence the database is messed up.
Jay
| |||||
| 1525.2 | Here they are | BYBLOS::TAMER | Mon Oct 14 1991 17:54 | 31 | |
re .1 Hi Jay, Here are the attributes (they start with QMS_) DNS> show obj .qms.repos know attr Attribute (Set) ______ DNS$ACS Attribute (Single) ___ DNS$Class Attribute (Single) ___ DNS$ClassVersion Attribute (Single) ___ DNS$UID Attribute (Single) ___ DNS$UTS Attribute (Set) ______ MCC_Class Attribute (Set) ______ MCC_DOMAIN_LIST Attribute (Single) ___ MCC_UID Attribute (Set) ______ MCC_Version Attribute (Set) ______ QMS_ALTNAMES Attribute (Single) ___ QMS_FILENAME Attribute (Single) ___ QMS_LOGNAME Attribute (Single) ___ QMS_QSYSTEM Attribute (Set) ______ QMS_SERVERS MSL IDCODES: QMS_ALTNAMES: 8026 QMS_FILENAME: 8027 QMS_LOGNAME : 8028 QMS_QSYSTEM : 8030 QMS_SERVERS : 8058 | |||||