|
HP OpenVMS Systemsask the wizard |
|
The Question is:
We use a custom command procedure CONFIGNET.COM to configure DECnet on each
node in our network. CONFIGNET.COM is the same on each node. At the top we
use F$GETSYI to get the nodename and address and put them in symbols that
are used later to set variou
s DECnet parameters.
Our procedure for changing a nodes name/address is to update MODPARAMS.DAT
(SCSNODE and SCSSYSTEMID), AUTOGEN system system, reboot, run CONFIGNET.COM,
reboot, and all is well. We follow the standard of SCSSYSTEMID being DECNET
area*1024 + DECNET node nu
mber.
There was a recent change to the CONFIGNET.COM that changed the F$GETSYI
calls using different 'items' as arguments. I do not know where these
'items' are derived from so I don't know what effect that will have on the
procedure above.
Old:
$ ID = %X'F$GETSYI("NODE_SYSTEMID")'
$ AREA = ID / 1024
$ NODE_NUMBER = ID - (AREA * 1024)
$ ADDRESS := 'AREA'"."'NODE_NUMBER'
$ NODE = F$GETSYI("NODENAME")
New:
$ NODE = F$GETSYI("NODENAME")
$ NODE_NUMBER = F$GETSYI("NODE_NUMBER")
$ AREA = F$GETSYI("NODE_AREA")
$ ADDRESS := 'AREA'"."'NODE_NUMBER'
Where do NODE_NUMBER and NODE_AREA come from? DECNET parameters? Derived
from SYSGEN parameters?
Thanks
The Answer is : The DECnet node address sys$getyi/f$getsyi itemcodes are derived from the contents of the SCSSYSTEMID SYSGEN parameter, based on the formula SCSSYSTEMID = (decnet_node_area * 1024) + decnet_node_number)
|