Conference csc32::consolemanager

>Customer created an action : 

>	command = console$eventlist

>	user data = uuu.xxx.yyy.zzz 0 0 TCPIP

>Then he wanted to customize the eventlist, save et restarted the eventlist.

>As described page 12-21, the customizations are saved in
>CONSOLE$APP_DEFAULTS:CONSOLE$EVENTLIST.DAT_display_server_screen


>first problem :


>if user data is uuu.xxx.yyy.zzz no file is created and so no customizations are
>saved.

>user data must be of the following format : uuu 0 0 TCPIP
    
    As you have found you are restricted to using the nodename and not it's
    address. Since the "." character is the delimiter between the filename
    and extension portions the code would have to map these characters to
    an underscore or some such and it's simply not worth the work and
    besides nodenames are more mnemonic than an address anyway.


>second  problem :


>the documentation seems wrong ... the name of the file is then :

>MULTI-LINE_WINDOW.uuu_0_0 and not CONSOLE$EVENTLIST.DAT_display_server_screen
    
    Your correct! The documentation is wrong!
    
    The code will search for MULTI-LINE_WINDOW.uuu_0_0 when the action is
    run as the result of a filter starting it as an Action routine. The
    latter file-spec convention is searched for when you enter the
    CONSOLE EVENTLIST command interactively.
    
    The last person doing the documentation is Phil Gee but I have no
    idea if he's still around. Send a message to Rae Kung-Collier at
    MUZICK::KUNG to find out who the new do maintainer is.


    Regs,
       Dan

	I will contact  MUZICK::KUNG.

But main problem is that you can't save your customization if the node is
described as uuu.xxx.yyy.zzz !

Thanks for your answer.

Maria.

	Two customers have reported this problem.

Is this note enough to report the pb or should I IPMT ?

Maria.

>Is this note enough to report the pb or should I IPMT ?

    The following is a repost of part of .1
    
    
    >>user data must be of the following format : uuu 0 0 TCPIP
    
    >As you have found you are restricted to using the nodename and not
    >it's address. Since the "." character is the delimiter between the
    >filename and extension portions the code would have to map these characters
    >to an underscore or some such and it's simply not worth the work and
    >    besides nodenames are more mnemonic than an address anyway.
    
    Does this make sense? The point is that it's a restriction that you
    have top use the node-name. VMS uses a "." to delimit
    the file-name from the file extension and an Internet address contains 
    "."'s. PCM uses whatever's in the nodename field to create the
    file-spec for the customizations file. When you use the address
    instead of the nodename you now have TOO MANY PERIODS IN THE FILE
    NAME - VMS allows only one. As I stated above we could map the "."'s
    to an underscore but I don;t think it's worth the effort. Why would
    you want to use the address insteadof the nodename? Nodenames are
    easy to remember. I cannot support an IPMT. It would have to be a 
    request for enhancement.
    
    Regards,
       Dan

	But, you know what a customer is.

It's the second time that this pb is reported to me.

First customer accepted very well the fact once I explained him why.

Second one thinks that this is a bug which has to be reported and corrected.

The problem is not between a host name and an address, because AUBER.EVT.DEC.COM
is a valid domain NAME an address would be 1.2.3.4

This customer has several domains which contain same host name :

for example, one can imagine that AUBER.EVT.DEC.COM is different from
AUBER.VBO.DEC.COM. In our network this is not possible because AUBER is unique,
but customer networks aren't build like our's. 

You will have the same problem with  Decnet/OSI full name.

For example : LOCAL:.AUBER

thanks for your reply.

Maria.

    Thank you for your clarification! Indeed, the domain issue is something
    that needs to be addressed. I don't know if an IPMT is appropriate
    though as it could be consider an enhancement but that is not my 
    decision to make.
    
    Regs,
      Dan