TS/MP System Management Manual (G06.24+, H06.03+)

Configuring Objects in a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
3-19
Defining Attributes for Guardian and OSS Servers
•
IN specifies the name of the input file passed to the server in the startup message.
It can be a DEFINE name. If you omit this attribute, spaces are passed to the
server.
•
OUT specifies the name of the OUT file passed to the server in the startup
message. It can be a DEFINE name. If you omit this attribute, spaces are passed
to the server.
•
PARAM assigns a string value to a parameter name, which the PATHMON
process then sends in a PARAM message to each server process as it starts. You
can include multiple PARAM specifications for a server class, just as you can
include multiple ASSIGN specifications. (If you specified a backup processor for
the processor attribute, the PATHMON process automatically adds a PARAM for
the backup processor to the PARAM message.)
•
STARTUP specifies a character string sent to the server in the startup message.
•
VOLUME specifies the volume and subvolume names to be passed to the server
in the startup message. If you omit this attribute, the defaults are those set with
the CMDVOL command.
These commands defines a Guardian SERVER object and then adds it under the
server class name ORDER-SRV:
= RESET SERVER
= SET SERVER PROCESSTYPE GUARDIAN
= SET SERVER ASSIGN ORDERS, $DATA.REG1.ORDFILE
= SET SERVER ASSIGN PARTS, $DATA.REG2.PARTFILE
= SET SERVER CPUS (2:4,3:5,0:6)
= SET SERVER MAXSERVERS 5
= SET SERVER NUMSTATIC 3
= SET SERVER PARAM SWITCH-1 “ON”
= SET SERVER PROGRAM \SYS.$DATA.SRVRS.ORDSRV
= ADD SERVER ORDER-SRV
The SET commands in the preceding example establish these characteristics for the
SERVER:
•
This is a Guardian server. (PROCESSTYPE attribute.)
•
The files that your server program recognizes by the names ORDERS and PARTS
are the files $DATA.REG1.ORDFILE and $DATA.REG2.PARTFILE, respectively.
(ASSIGN attribute.)
•
The PATHMON process starts the first server process in the server class in
processor 2, the second server process in processor 3, and the third in processor
0.
If processor 2 is down, the PATHMON process instead starts the first server
process in processor 4 as the backup processor for the first process. Similarly,
CPUs 5 and 6 are the backup CPUs for the second and third server processes,
respectively. If the PATHMON process starts more than three server processes, it