|
Hello,
Are my questions so stupid that nobody wants to answer them (this is
not my first question that remains without any answer) ?
I do need some explanation on the way the DIRECTORY directive works
with the Registration FM.
The directive was working at a certain point of the development of my AM
and I haven't re-use it till now because I am writting the user's guide
and looking for an example of each supported directive to put in the
documentation. An now the directive fails ...
Thanks again for any help.
Regards,
sylviane.
|
|
RE:.0
When you issus "MCC> dir sare *", the DECmcc searches the 'ENTIRE'
namespace for DNS objects with MCC_Class equal to MCC_K_Class_SARE.
When a DNS object's MCC_Class attribute value matches, DECmcc will
read a binary attribute which stores the identifiers (e.g. in SARE
global entity, the identifiers are Equipment, Domain, etc.)
The identifiers are ILV-encoded. The binary attributes are not
visible from V1.1 DNS$Control, but readable using V2.0 DNS (both
VMS and Ultrix). If you do not have access to V2.0 DNS, I have a
utility program which enumerates a DNS object's attributes including
the binary attributes (send me mail TOOK::kwak if you need the program).
However, when the binary attribute does not exists, DECmcc returns
the error message - "%MCC-E-NOATTRIB".
This binary attribute is created in mcc_dns_create_instance().
To fix your problem, you have to delete the DNS object which was
partially created by DECmcc.
Assuming that you are running V1.1 DNS, and your SARE object was tried
to be registered in the root directory:
DNS>! find the MCC_Class value in hexadecimal
DNS> sho object .LEG001 attribute MCC_Class
DNS> show dir . known objects
DNS>! for each DNS object (say foo), see if it has MCC_Class attribute
DNS> show object .foo attribute MCC_Class
DNS>! if the MCC_Class matches the MCC_Class of your SARE object .LEG001
DNS>! Issue the following MCC command, and if you get
DNS>! "Not Registered Entity = SARE ..............",
DNS>! delete the DNS object (DNS> delete object .foo)
DNS>! MCC> dir SARE .foo
William
|
|
Hello William,
Thank you for your explanations, the problem is exactly what you have
described. In subsequent tests, I have noticed other symptoms of the
problem : it was impossible to DEREGISTER or REGISTER the object.
Following your suggestions, I have deleted the partial registered DNS
object, registered again the object and the DIRECTORY directive works
fine again.
Thank's again for spending time to answer to my problem.
Best regards,
sylviane.
|