NET/MASTER Management Services (MS) System Management Guide

Moving the DSNM Subvolume
Configuring NonStop NET/MASTER MS
115414 NonStop NET/MASTER MS System Management Guide 3–17
Setting a Unique Domain ID For the Inter-System Routing (ISR) component to work properly, each system
connected on the network must have a unique domain ID. Systems that possess the
same domain ID cannot exchange messages with one another.
NonStop NET/MASTER MS derives a default domain ID from the first four characters
of the system name. For example, the domain ID of a system named \GANKER is
GANK. If a network includes, for example, systems named \REST41 and \REST42,
the systems have the same default domain ID: REST. The two systems can exchange
messages properly only if you change the domain ID on one of the systems to
something other than REST.
Use the DID operand to set the domain ID of a system. For example, to set a domain
ID of RS41, include the following command in the CONFIG file:
PARAM DID=RS41
You can specify a domain ID of one through four alphanumeric characters. If the
system is unnamed, the character string ANON becomes the domain ID.
Disabling Use of
Multiple Guardian User
IDs
If a user ID definition record includes more than one GUID, users with access to the
OPSYS or PROGRUN commands can invoke Guardian utilities and application
programs under any of the GUIDs in the user ID definition record. See Section 4,
“Managing User Access and Privileges,” for an explanation of GUID assignment.
If you want to disable the capacity for using more than one GUID, include the
following command in the CONFIG file:
PARAM SWGUID=NO
Although users can operate with only one GUID at a time, if SWGUID is set to YES,
users can use different GUIDs without logging off NonStop NET/MASTER MS.
Moving the DSNM
Subvolume
By default, the DSNM files reside on the NonStop NET/MASTER MS installation
volume in the ZDSMS subvolume. If you move either the DSNM files or the NCP
program file such that the DSNM subvolume and the NCP program file are no longer
on the same volume, you must inform NonStop NET/MASTER MS of the DSNM
subvolume location.
Use the DSNMSUBVOL operand to specify the location of the DSNM files. For
example, if the NCP program file is on an ISV named something other than $DATA1
and the DSNM files reside in a subvolume named $DATA1.ZDSMS, change the
CONFIG file to include this command:
PARAM DSNMSUBVOL=$DATA1.ZDSMS
If you integrate NonStop NET/MASTER MS with an external DSNM environment or
if you configure one or more DSNM processes in the CONFIG file, the value of the
DSNMSUBVOL operand is ignored. Section 11, “Configuring the Processing
Environment,” discusses the procedures used to configure DSNM.