Conference azur::mcc

309.0. "Insufficient Info about "Advanced Registration Requirements"" by BYBLOS::TAMER () Thu Sep 06 1990 16:47

I am doing the following:

MCC> register server .server.x synonym=x, node=byblos, associ=tp$ssc
server TPEDNS_NS:.server.x
AT  6-SEP-1990 10:28:39


Registration Successful

MCC> dir server .server.x
server TPEDNS_NS:.server.x
AT  6-SEP-1990 10:29:24


Directory successful.
                                   Name = TPEDNS_NS:.server.x
                                synonym = x
MCC>

When I issue 
MCC> show server x all char

Question set #1:
*************
My AM is getting TPEDNS_NS:.x as instance name.  Is this correct ? Who is 
inserting this TPEDNS_NS:., the FCL ?  

I assume I can strip off TPEDNS_NS:. but then what is the purpose of the 
synonym ?

Question set #2:
------------

I need to read the node and association attributes from DNS given that I 
get passed the synonym (If I get passed the fullname, that is trivial and is
working). I assume that I have to call mcc_dns_translate_ident to get the 
primary identifier and then I can call mcc_dns_read_attr_data. Is this correct ?

The problem is that I tried to call mcc_dns_translate_ident with the instance
passed to my AM, i.e. TPEDNS_NS:.x, but I get MCC_S_NOENTITY (which I expected).
Also when I call mcc_dns_translate_ident with instance x, I get the same cvr 
(which I did not expect).


What is really needed is complete documentation in the MM-programming manual
about the "advanced registration rtequirements" in appendix E.

But for now, I would like some quick answers.


Thanks,
Phil

    Phil,
    
    Did you ever get these questions answered?
    
    FYI - if you define an attr/arg/inst as a fullname or simplename
    the PMS (Iconic and FCL) will call the mcc_dns routines to translate
    them into internal format.s