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

Configuring Objects in a PATHMON Environment

NonStop TS/MP System Management Manual—541819-001

3-8

Configuring PATHMON-Controlled Objects

After specifying global limits and issuing the START command, you configure the

SERVER objects that run under the PATHMON process to support your application.

If your environment includes the Pathway/iTS product, you also configure TCP, TERM,

and PROGRAM objects. For instruction on configuring these objects, see the

Pathway/iTS System Management Manual

You create and control objects by defining and changing their attributes. PATHCOM

maintains a list of attributes that describe configuration information for each object:

how it relates to other objects and how it should be managed by the PATHMON

process. The attributes for a server, for instance, specify the server name, the server

type (Guardian or OSS) the CPUs on which the server runs, the server’s execution

priority, the name of the program the server runs, and other characteristics.

Using the SET and ADD Commands

Whether you create objects for a new environment or add objects to a restarted

environment, the technique is the same, as follows:

1. Define the attributes for the object, using a SET command parameter for each

attribute.

As you define these attributes, PATHCOM checks them for syntax errors.

PATHCOM saves the attributes in memory, pending your request to add the

object. In many cases, you can choose to accept default values supplied by

PATHCOM.

When creating objects, be sure to set proper defaults so that objects are created in

the appropriate location. When creating Guardian server classes, use the

CMDVOL command to set the default node, volume, and subvolume for the

expansion of any file names. When creating OSS servers, use the CMDCWD

command to record an OSS directory to be used to resolve relative file names

specified for OSS server attributes. For more details on these commands, see

CMDVOL Command on page 10-3 and CMDCWD Command on page 10-2.

If you do not specify a node name as part of the file name for a process or device

in a configuration, the default node for the file-name expansion is affected by any

values you specify for the NODEINDEPENDENT attribute of the SET PATHWAY

command or for the node portion of the CMDVOL command. The node name

used is the node on which the PATHMON process is currently running if any one of

this situations applies:

•

You set the NODEINDEPENDENT attribute of the SET PATHWAY command

to ON and you omit the node name in the parameter.

•

You set the node name to \* in a CMDVOL command and you omit the node

name in the parameter.

•

You specify \* for the node name in the parameter.