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

Configuring Objects in a PATHMON Environment

NonStop TS/MP System Management Manual—541819-001

3-16

Choosing Names for PATHMON-Controlled Objects

When adding multiple objects of any one kind, you should name them in a logical way

that makes them easy to identify and manage later. For example, you might name

SERVER processes according to the functions they perform: ORDERS for a SERVER

that processes orders or INV for one that updates inventory control records.

For large PATHMON environments with numerous objects, the names you assign are

particularly important for identifying and managing objects. The names you choose can

help you identify and relate objects when displaying information about your PATHMON

environment.

When you issue a command that uses an asterisk (*) to operate on an entire class of

objects−for example, STOP SERVER *−the objects are processed in alphabetic order.

Names for SERVER objects can contain from 1 to 15 alphanumeric or hyphen

characters. Names must start with a letter; must be unique within the PATHMON

environment; and cannot be a PATHMON reserved word.

Configuring Server Classes

The SERVER object represents a server class. A server class is a group of processes,

all of which execute the same object program. A server process is an executing server

program.

If your system supports both the Guardian and the OSS operating environments, you

can configure both Guardian server classes and OSS server classes. (To support both

operating environments, your system must be a RISC-based, NonStop server and it

must have the OSS software running.) Guardian and OSS servers operate the same

way and share many attributes. There are some differences in how they are

configured, however. These differences are outlined in this subsection.

You use the SET SERVER and ADD SERVER commands to define the attributes for a

server class, name the server class, and add it to the system.

If your system has a NonStop TUXEDO system running in the OSS operating

environment, you might also have installed the Pathway translation server for NonStop

TUXEDO. This special-purpose OSS server enables SCREEN COBOL requesters to

access NonStop TUXEDO application services indirectly, through the TCP. (The

server can also be used by Pathsend requesters.) The translation server is described

in the

Pathway Translation Server for the NonStop TUXEDO System Manual

Configuring Static and Dynamic Server Processes

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

server process that the PATHMON process creates when the START SERVER

command is issued. A dynamic server is a server process that the PATHMON process

creates after a link manager has waited for a specific time period for a static server to

become available. The time period is determined by the CREATEDELAY attribute for