| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1832.1 | is this working yet? | TOOK::CALLANDER | MCC = My Constant Companion | Wed Jan 08 1992 10:08 | 4 |
| Raimondo,
have you got this working yet?
|
| 1832.2 | Can have ONE AND ONLY ONE Primary Identifier | TOOK::TAN | Ed Tan | Wed Jan 08 1992 11:18 | 36 |
| First of all, in the SRM V1.1, section 7.5.1.8 Syntax of an Attribute
and Attribute Partition Definition, the explanation on the use of
DNS_IDENT says:
"DNS_IDENT The management module must choose one and only one
identifier to be the DECdns PRIMARY_NAME of the global entity. This
property may not be used for identifiers of non-global classes.
..... If the identifier attribute is not to be the DECdns
PRIMARY_NAME, but is to be a valid identifier used for lookup in the
DECdns namespace then DNS_IDENT = ALTERNATE_NAME. ......"
What this means is for each global entity class, there must be
ONE AND ONLY ONE primary identifier (DNS_IDENT = PRIMARY_NAME) in the
MSL file of this class. Other identifiers can be defined for this
class, and if they are to be used as alternate identifiers for lookup
in the namespace, DNS_IDENT must be set to ALTERNATE_NAME.
It looks like in the MSL file for your global entity class,
you might have more than ONE identifier defined with DNS_IDENT =
PRIMARY_NAME. So when REGISTRATION FM tries to add this second
identifier (with DNS_IDENT = PRIMARY_NAME) to the namespace using
kernel routine mcc_dns_add_identifier, this complains that the
DNS_IDENT value is wrong and returns the following error,
MCC-E-INV_DNSIDENT, specified identifier attribute is not valid for
instance lookup
Would you verify your MSL to see if this really is the case. If
not, may be you could post your definition of IDENTIFIER attributes
from your MSL in here.
/Ed
|
| 1832.3 | It Works | ROM01::LILLI | | Wed Jan 08 1992 11:49 | 13 |
| Hello,
I solved my problem, now my registration directive works. The problem
was that I did not use the MCC_DNS_OPAQUE_FULLNAME because inside the
SRM and MM programming is not clear that if you what to use the
register directive you must use the MCC_DNS_OPAQUE_FULLNAME.
It will be nice if someone could update the MM programming.
Thanks
Raimondo
|
| 1832.4 | which Management Module Programming (MMP) are you using? | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Wed Jan 08 1992 13:53 | 10 |
| RE: .3
>> the SRM and MM programming is not clear that if you what to use the
>> register directive you must use the MCC_DNS_OPAQUE_FULLNAME.
>>
>> It will be nice if someone could update the MM programming.
Raimondo -- Are you using the t1.2.4 version of the MMP manual ?
/keith
|
| 1832.5 | V 1.2 | ROM01::LILLI | | Thu Jan 09 1992 07:56 | 14 |
| Hello Keith
I'm using the following manual:
DECMMC_MM_PROGRAMMING_V1_2_FT.PS;4 7202/7203 5-NOV-1991
Inside this manual I cannot find any indication about the use of
MCC_DNS_OPAQUE_FULLNAME.
Any Idea ?
Thanks
Raimondo
|
| 1832.6 | Information about the DNS routines must be added to the MMP Registration | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Thu Jan 09 1992 09:18 | 15 |
| RE: .5
> I'm using the following manual:
> DECMMC_MM_PROGRAMMING_V1_2_FT.PS;4 7202/7203 5-NOV-1991
>
> Inside this manual I cannot find any indication about the use of
> MCC_DNS_OPAQUE_FULLNAME.
Raimondo -- We have a problem here. There *is* a section in the Management
Module Programming (MMP) guide, Appendix C, but it never talks about using
the DNS routines. I haven't looked at the SRM yet - but the MMP guide should
go into this bit of detail. I'll QAR the toolkit
thanks,
keith
|