Pathway/XM System Management Manual

Configuring Servers
Compaq NonStop™ Pathway/XM System Management Manual426761-001
6-3
Example
Example
For example, the following sequence of PXMCFG statements defines a SERVER object
and then adds it under the server-class name ORDER-SRV:
RESET SERVER
SET SERVER NODE SERVER-1
SET SERVER PROGRAM $DATA.SRVRS.ORDSRV
SET SERVER GROUP ORDERS
SET SERVER GROUP THURSDAY
SET SERVER CMON ON
SET SERVER HIGHPIN ON
SET SERVER MAXSERVERS 5
SET SERVER NUMSTATIC 3
SET SERVER NONSTOP 0
SET SERVER TMF ON
SET SERVER ASSIGN ORDERS, $DATA.REG1.ORDFILE
SET SERVER ASSIGN PARTS, $DATA.REG2.PARTFILE
SET SERVER PARAM SWITCH-1 ON
ADD SERVER ORDER-SRV
The SET statements in this example establish the following characteristics for the
SERVER object:
The system and the CPU resources used for server processes in this server class, as
well as any specified attribute defaults, are defined in the NODE object SERVER-1.
The object code for the server class is stored in the file $DATA.SRVRS.ORDSRV.
The server class is managed as a distributed server class (because the TYPE
attribute is not specified and its default is DISTRIBUTED).
The server class is defined as a member of two server groups: ORDERS and
THURSDAY.
Before creating each new server process, Pathway/XM will send a message to the
user-supplied $CMON process, if any, allowing $CMON to approve or modify the
process startup parameter values.
Server processes in this server class will run using high PINs.
The total number of server process reservations that can be distributed for the server
class is 5.
The total number of server process reservations and started servers that are
permanently allotted to this server class per PATHMON process is 3.
Server processes in this server class will not be run as process pairs.
The relative priority at which processes in this server class will run is determined by
the setting of the PRI attribute of the NODE object SERVER-1 (because no PRI
attribute is specified for the server class).
Send operations from requesters to processes in this server class are allowed
whether or not the SCREEN COBOL or Pathsend requester program is in TMF
transaction mode.