NET/MASTER Management Services (MS) System Management Guide

Specifying System File and Subvolume Locations
Configuring NonStop NET/MASTER MS
115414 NonStop NET/MASTER MS System Management Guide 3–3
If an error in the CONFIG file prevents NonStop NET/MASTER MS from starting, an
event message is issued. Refer to the NonStop NET/MASTER Messages Manual for
additional information about event messages generated by NonStop NET/MASTER
MS.
Restricting Use of a
CONFIG File
You can restrict the use of a particular CONFIG file to a specific NonStop
NET/MASTER MS system. A CONFIG file that contains the PROCESSCHAR
operand can be used only by a NonStop NET/MASTER MS system whose NCP name
begins with the same character as that specified by the PROCESSCHAR operand. For
example, to restrict the use of a CONFIG file to a system whose NCP is named
$LNNM, include the following statement in the CONFIG file:
PARAM PROCESSCHAR=L
If you direct NonStop NET/MASTER MS to use a CONFIG file whose
PROCESSCHAR argument differs from the first character of the NCP name, the
NonStop NET/MASTER MS system issues an Event Management Service (EMS) event
message and fails to start.
Note If the name of the NCP begins with Z, do not use either X or Y as arguments for the PROCESSCHAR
operand for a CONFIG file used with another NonStop NET/MASTER MS system; the NonStop
NET/MASTER MS system whose NCP name begins with Z can create processes whose name begins
with X or Y, as well as Z. Tandem reserves the use of process names that begin with X, Y, and Z.
Specifying System File
and Subvolume
Locations
The locations of certain system files and subvolumes are determined during system
startup and stored in global memory. If you change the name of a select file or the
location of a select library, you must specify the new name of the file or library by
including PARAM commands in a CONFIG file.
The NCP operates as if all other NonStop NET/MASTER MS files reside on the same
volume as the NCP program file. Therefore, if you move subvolumes to other
volumes, you must explicitly specify the location of each program file and subvolume
for which there is a PARAM command operand.
Specifying NCL Procedure
and Library Locations
This subsection discusses how to specify NCL procedure and library locations. It
includes the following topics:
Specifying user procedure libraries
Specifying customized and distribution procedure libraries
Specifying object files for user, customized, and distributed NCL procedures
Specifying the distributed NCL object file
The default NCL procedure search path