Release Notes for LABSTATION 23

1. A remote node name may not be defined more than once on the VAX. Doing so
prevents the remote node from network initializing. The node will load but 
will not allow the network to comeup.

	For example:
	
ASSUME:
	ARGON is defined as node 11 on a DMR communications device.
THEN:
	RMCONFIG is run. Node 8 on device DMP-0 is defined as ARGON.
RESULT:
	Remote node ARGON will not node initialize.

	However, 

ASSUME:
	ARGON is defined as node 9 on device DMP-0 and NEON is defined as 
	node 10 on device DMP-0.
THEN:
	RMCONFIG is run with ARGON defined as node 10 and NEON defined 
	as node 9 on device DMP-0.
RESULT:
	Remote node ARGON will become node 10 and NEON will become node 9
	on the new network.

	The difference between these two is that in the first, the data
for device DMR is maintained in the new data base. As a result, the node
ARGON sees itself listed as another node in the system. In the second
case, since the device DMP-0 was being reconfigured, all previous data
on that device is purged by RMCONFIG so there is no conflict.

2. If an account other than the system manager is logged into more than 
once and a LOAD NODE command is issued from within that account, the
LOAD instruction will fail. The only account account that can issue
a LOAD NODE and be logged into more than once is the system manager account.
To correct the error do not issue the LOAD NODE command while logged into
an account that is already logged into.