Conference azur::mcc

The user can specify which identifier (only one though) s/he wants displayed 
under the icon.  This is done by editing the resource file MCC_RESOURCE.DAT 
and adding the resource

mcc_pml.map_alt_id.<class-name> : <identifer attribute code>

Or in your case it was done by modifying an existing resource.

To get it the user can do the following (yes I know it is ugly but this
stuff was never intended to be made public):

$mana/too/dict
DAP> sho class node4 attribute_partition identifiers definition attribute_list

   Definition Name = ATTRIBUTE_LIST
   Type = L   Length = 4   Count = 3   Defined = TRUE   Class = S
   value[1] = 1
   value[2] = 2
   value[3] = 160

DAP> sho class node4 attribute code 1 definition presentation_name

   Definition Name = PRESENTATION_NAME
   Type = T   Length = 4   Count = 1   Defined = TRUE   Class = S
   value[1] = "Name"

DAP> sho class node4 attribute code 2 definition presentation_name

   Definition Name = PRESENTATION_NAME
   Type = T   Length = 7   Count = 1   Defined = TRUE   Class = S
   value[1] = "Address"

DAP> sho class node4 attribute code 160 definition presentation_name

   Definition Name = PRESENTATION_NAME
   Type = T   Length = 15   Count = 1   Defined = TRUE   Class = S
   value[1] = "Registered Name"


If the user wanted the attribute "Name"  to be displayed under the icon 
s/he would put the line

 mcc_pml.map_alt_id.node4: 1

Hello,

	Thanks for the information. I think it is wrong to say that this
information should/is not public, because at the field-test training last
October the displaying of alternate identifiers was discussed. Are there
any future plans to extend this feature, i.e. more than one identifier or
the possiblity to change the identifier through the iconic map, or to choose
for some nodes the name and other nodes the address? I was under the impression
that this information would be stored in the map-files not the resource.dat,
thereby making it much more customizable? 

Julie Ann

Julie Ann,

  I didn't say it was not public.  I said it was never intened to
be made public.  We obviously made it public but do not have an
adequate interface for it.  Providing the interface for the existing
alt id support is high on the 1.3 list of things to do.  Ease of use 
takes HIGH priority for the next release.  Extending it to display
more than one identifier (or even let the user decide what to call
it regardless of its identifiers) would also be a nice feature. 

  Currently the code allows for the user to say which identifier
should be used for ALL instances.  If I understand your note you 
would like to be able to choose which identifier for an individual
instance.   I added it to the wish list.

/Jim

    Hi Jim,
    
    
    	I didn't mean to sound nasty or anything. It is a customer
    requirement to have such features (which were available in Ethernim)
    available as soon as possible in DECmcc. By in Ethernim, I mean that when
    you had selected a node it showed you automatically name, address, and
    other information. 
    
    You mention V1.3. Will there be another version between 1.2 and 2.0?
    What are the time frames for this release and will the wish list be
    made public, or atlease Digital Internal?
    
    Julie Ann
    
    

    Hi Julie Ann,
    
      It isn't clear if the next release is going to be 1.3 or 2.0.  
    DECmcc engineering is in the process of working out what the next 
    release should contain so it would be premature for me to give
    any dates/functionality.    
    
      You can help us figure out what should go into the next release 
    by replying to note 2926 with your suggestions/requirements.
    
    Thanks
    /Jim