TS/MP 2.5 System Management Manual

Using Existing Object Attributes for New Objects
You can use object definitions recorded in the PATHMON configuration file as the basis for defining
values in the PATHCOM working set. For example, suppose that you want to add a new SERVER
object named JACK, using the same attributes that applied to the SERVER named ANNA (except
for the TMF attribute). You could do this by using the SET command with the LIKE option, as
follows:
= SET SERVER LIKE ANNA
= ADD SERVER JACK, TMF ON
The LIKE option requests PATHCOM to set the working-set values exactly the same as those for
the attributes of the object whose name follows LIKE. This feature is useful for defining and adding
multiple objects of the same kind with similar definitions. For example, when specifying multiple
SERVER objects, you need enter only those attributes that are different from those of a previously
added SERVER. Alternatively, you can define a SERVER that is exactly like a previously added
SERVER.
Choosing Names for PATHMON-Controlled Objects
When adding multiple objects of any one kind, you must 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
run 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 allows SCREEN COBOL requestors to access NonStop TUXEDO application services
indirectly, through the TCP. (The server can also be used by Pathsend requestors.) The translation
server is described in the Pathway Translation Server for the NonStop TUXEDO System Manual.
NOTE: PDMCOM or PATHCOM can be used for configuring server classes in TS/MP 2.5
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 2.5 Release Supplement.
Configuring Server Classes 61