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

Configuring Objects in a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
3-21
Defining Attributes for Guardian and OSS Servers
These commands defines an example of an OSS SERVER object and then adds it
under the server class name ORDER-SRV1:
= RESET SERVER
= SET SERVER PROCESSTYPE OSS
= SET SERVER ARGLIST -1, process/log, -t
= SET SERVER CPUS (2,3,0)
= SET SERVER CWD /centrl/inven/orders
= SET SERVER DEFINE =PARTS, CLASS MAP, FILE $DATA.REG2.PRTFIL
= SET SERVER DEFINE =ORDERS,CLASS MAP, FILE $DATA.REG2.ORDFIL
= SET SERVER ENV DEBUGLOGFORMAT=TRUE
= SET SERVER ENV HANGAROUND=TRUE
= SET SERVER MAXSERVERS 4
= SET SERVER NUMSTATIC 3
= SET SERVER PROGRAM app/bin/ordsrv1
= SET SERVER STDERR process/error
= SET SERVER STDIN process/orders/new
= SET SERVER STDOUT process/orders/out
= ADD SERVER ORDER-SRV1
•
This is an OSS process. (PROCESSTYPE attribute).
•
As shown by the -1 and process/log values in the arglist, the process logs requests
and responses in an OSS file with the absolute filename
/centrl/inven/orders/process/log. (The server code must get the OSS current
working directory information from the CWD attribute and add it to the filename
“process/log” to produce the full, absolute pathname.)
The -t value indicates that a timestamp is associated with each request and
response. (ARGLIST 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 the PATHMON process starts more than three server processes, it reuses the
CPUs in the order specified; a fourth server process, for instance, would start in
processor 2 if that processor were available.
If processor 2 is down, the PATHMON process instead starts the first server
process in processor 3. If processor 3 is down, the PATHMON process starts the
first server in processor 0. (CPUS attribute)
•
The OSS current working directory for this server process is /centrl/inven/orders.
Relative filenames like those specified for the PROGRAM and STDERR, STDIN,
and STDOUT attributes are resolved against this directory name to create an
absolute pathname. (CWD attribute.)
•
PARTS is defined as the logical filename for the physical file located at
$DATA.REG2.PRTFIL. ORDERS is defined as the logical filename for the
physical file located at $DATA.REG2.ORDFIL. (DEFINE attribute).
Note. The server program name is always passed as the first argument in the arglist,
regardless of what you specify in the arglist.