Conference azur::mcc

    The name appearing with the icon is always the "instance" name
    of the global entity.  We get it from the domain fm and plop it
    on the screen verbatim.
    Is it that you would like to see it in a different format?
    
    Fred
    

    
    I just reread your note...Are you refering to the upcasing?
    

  
>    Could someone explain following (I'm using IFT):
>    as Node4 Entity that you enter Entity in form of 
>    .DNA_Node.<Node name> (I've used command file provided with
>    the kit to populate the namespace).
>

  For this the ADD operation does the FCL equivilent of 

	REGISTER Node4 .DNA_Node.<Node name> SYNONYM = <synonym>
   
>    If I try to add node with .<Node name>, it will result to different
>    sequences of errors depending how you continue (acces violations, 
>    even possible stack dump) which probably have been all tested and 
>    reported as QARs?

  The ADD operation, in this case, would do the FCL equivilent of:

	REGISTER Node4  .<Node name> SYNONYM = <same synonym as above>

  I am assuming that the synonym is the same in both cases.
  If this is so, you should get the error  

        The requested operation cannot be completed
               MCC Service Error = Registration Failed: Duplicate Synonym

   In my testing, however, I got back (only once) the message    
   
         The requested operation cannot be completed
             MCC Service Error = Internal Error Occurred in DECnet Phase IV AM.

   I will bring this to the attention of the DNA4 development team.

>    Now the entity shows up in the map with text .DNA_NODE.OLLI
>    for example. Is there any way of getting it show different 
>    name on the map?

   Nope.  The name required for the register directive is the name used in
   the map.   This might be allowd in the V1.2+ timeframe.

/Jim
    
   

    Ok, I got that.
    
    The errors like : Map window message 002726F4 + The requested operation
    cannot be completed, Dispatch entry for the specified entity does not
    exist, Default verb SHOW unavaialable; specify verb - are caused
    by the access violations and code running wrong tracks...
    
    Thanks for notifying engineering.
    
    Now to orginal question : Did anyone consider that naming on the map 
    would be based on something else than DNS name for entity ?
    What I tried to do was to get just the node name (or synonym in fact)
    on the map.
    I suppose what you say means that an additional "map nickname" field
    should added to entity information (Reference info?)?
    
    Olli

Yes we did consider this because it is a nice feature.   We were not,
however, able to schedule it for the v1.1 product.

 
/Jim