[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

1558.0. "Access towerset" by PARZVL::SHIAU () Thu Sep 26 1991 16:42

We are currently writing a Functional Module that processes both Phase IV and 
Phase V nodes. Can anyone help me on how to use Towerset as the entity to make 
the mcc_call_access instead of using the node name on Phase V AM calls? Plus 
how to parse this out_p containing the towerset after the mcc_ilv_get to get 
the NETs? 

I understand I can always call dns to get backtranslation softlink and get a 
node name from the softlink, but first, I am not supposed to do it from FM,
second, the backtranslation links I have may not necessary exist in the 
namespace and finally, I need to know how to parse the towerset in order to do 
that. 

I've done some test to use node name to retrieve the towerset and then plugged 
the towerset back as the in_entity and issue the call equivalent to FCL "show 
node xxxx all id", but with no luck. 

I also couldn't find out any documentation that decribes the towerset structure 
except the information from the ilv dump of the out_p. I'll appreciate any 
information. Thank you in advance.

Jerry S.
T.RTitleUserPersonal
Name		DateLines
1558.1try Arun for dna5 questionTOOK::CALLANDERMCC = My Constant CompanionThu Oct 03 1991 10:367
    
    Could you please send your request off-line to Arun Sankar. She should
    be able to help. Then when done could you post a synopsis of what you
    have learned. Thanks
    
    (Arun is located at took::sankar)
1558.2Needs more work..TOOK::JESURAJTue Oct 15 1991 13:2213
    Right now mcc_dns_translate_identifier routine does not suuport the 
    translation of tower set into fullname. It is a bug and is being worked
    on. Once this is fixed there should not be problem in solving the
    problem stated .0.
    
    Since   mcc_dns_translate_identifier is a well documented routine
    in SRM, any MM can use it. I don't see any reason why FM should not 
    use it.  However, in this case it is beeter to fix the phase V AM to 
    do this translation.
    
    
    
    .. Jay
1558.3It definitely does!SWORD1::ESEugene ShvartsmanTue Oct 15 1991 16:4535
    Jay,

    1) I assume you are talking about mcc_dns_translate_ident routine?

    2) I won't call it "well documented routine".

       - As everywhere in SRM nothing is mentioned which fields of
       MCC_T_Descriptor structure should be set and to what values. I mean
       Primary_Entity_Id parameter.

       - As to regards of the Entity_Spec parameter which "is the address of the
       entity specifier structure containing alternate identifier", we still
       don't know what is it - a towerset.

       When Jerry have mentioned:

>I've done some test to use node name to retrieve the towerset and then plugged 
>the towerset back as the in_entity and issue the call equivalent to FCL "show 
>node xxxx all id", but with no luck.

       it has been the best what we have been able to do.

       We still need 

> any documentation that decribes the towerset structure 

       because we HAVE TO BUILD towersets from NSAPs or NETs. Routing layer
       doesn't return towerset as an attribute.

       We still

> I'll appreciate any information. Thank you in advance.

       Thank you,
       Gene
1558.4Will post some details soonTOOK::JESURAJWed Oct 23 1991 14:0427
    ref .-1
    
>>    1) I assume you are talking about mcc_dns_translate_ident routine?

    Yes I am talking about the same.
    
>    2) I won't call it "well documented routine".
>
>       - As everywhere in SRM nothing is mentioned which fields of
>       MCC_T_Descriptor structure should be set and to what values. I mean
>       Primary_Entity_Id parameter.

>       - As to regards of the Entity_Spec parameter which "is the address of the
>       entity specifier structure containing alternate identifier", we still
>       don't know what is it - a towerset.

    
    I will try to fill this hole here at least for the towerset  once I have
    completed the support and tested it. I will post it here soon.
    
    
    Jay