TS/MP System Management Manual (H06.05+, J06.03+)

HP NonStop TS/MP System Management Manual—541819-007

4-1

Starting and Stopping SERVER

Objects

After you configure and start your PATHMON environment and define and add

SERVER objects, you issue the START command to activate each SERVER object or

process.

When the PATHMON process runs the START command, it checks the status of the

object named and then performs the operations needed to start the object.

Starting SERVER Objects

To start a server class, an individual server process in a server class, or all server

classes controlled by a given PATHMON process, use the START SERVER command.

There are two types of server processes: static and dynamic.

•

A static server is a server process that the PATHMON process creates when you

issue the START SERVER command.

•

A dynamic server is a temporary server process that is started by the PATHMON

process under certain circumstances. This type of server is not dependent on the

START SERVER command.

For more information about static and dynamic servers and how you configure them,

see Configuring Server Classes.

Static Server Processes

When you issue a START SERVER command, the PATHMON process starts the

number of static servers defined for the server class. This number is defined by the

NUMSTATIC attribute in the SET SERVER command.

(You do not have to issue the START SERVER command for the PATHMON process

to create a static server process; the PATHMON process starts server processes as

they are needed. However, issuing a START SERVER command provides for better

startup and transaction performance. See Link Requests.)

Note. If your PATHMON environment includes objects provided by the Pathway/iTS product,

such as TCP s and TERM and PROGRAM objects, for information on starting and stopping

these objects, see the Pathway/iTS System Management Manual.

Note. PDMCOM or PATHCOM can be used for starting and stopping SERVER objects in

TS/MP 2.3 (or later version) PATHMON environment. However, it is recommended to use

PDMCOM (instead of PATHCOM) because it can communicate with multiple PATHMONs

simultaneously. For more information, see the TS/MP Release Supplement.