Article 154419 of comp.os.vms:
In article <01bb9a8d$401b0740$de3cd69f@per14115.peco.com>, "38.8.213.2" <rkennedy@nucgen.peco.com> writes:
> In DCL, you need to assign the DEC 90M a node name, via NCP.
>    example:     	mc ncp
> 		define node MYNODE1 <circuit id>   ! like 10.100 or whatever
> 		define node MYNODE1 hardware address <ethernet address>
> 
> Then, in LATCP, create a port that is assigned to that node.
>   example:	mc latcp
> 		create port LTA1x/application      ! where x is the port you have
> 						! your serial device attached.
> 
> Then, back in DCL, you can set various settings for the terminal device for
> 	that LTA1x  port, via set term LTA1x /perm/<settings>.

Two problems with this post.

1.  You're missing the LATCP SET command that establishes a default mapping
    between LTA port name and the actual DECserver port:

	$ MCR LATCP
	LATCP> SET PORT LTAx /NODE=MYNODE1 /PORT=PORT_2

2.  The DECserver node name as stored in the NCP database is completely
    ignored by LAT.  The DECserver has a separate name for LAT purposes.
    That name is stored in NVRAM on the server.  (Always remember,
    LAT != DECNET).

    I'm not familiar with the steps for setting that name on DEC 90M's.

    For other servers, you can see the node name with a SHOW SERVER
    command and set the name with a DEFINE SERVER NAME xxx command.
    The default server name is something like LAT_08002bnnnnnn,
    computed from the server's MAC address.

    You may want to look at the port names as displayed with SHOW PORT
    and possibly alter those names with DEFINE PORT n NAME xxx as well.

    The information in the NCP database is useful for setting up downline
    load/upline dump information and for letting you connect to the
    server with the console carrier interface.

	John Briggs			briggs@vitro.com