TS/MP 2.5 System Management Manual

8 Overview of PATHCOM
This section contains overview information to help you get started using PATHCOM to manage
your PATHMON environment. For more detailed information on how PATHCOM works and how
to manage your Pathway environment, see “Introduction to NonStop TS/MP System Management”
(page 17) through “Tuning Your System by Using Statistics” (page 117).
NOTE: This manual provides information specific to commands dealing with objects managed
through the NonStop TS/MP product. PATHCOM commands dealing with SCREEN COBOL
requestors, such as those operating on TCP, TERM, and PROGRAM objects, which are controlled
though the Pathway/iTS product, are described in Pathway/iTS System Management Manual.
NOTE: When using TS/MP 2.5, HP recommends that you use PDMCOM instead of PATHCOM,
because it can communicate with multiple PATHMONs simultaneously. For more information on
PDMCOM, see the TS/MP 2.5 Release Supplement.
Commands and Object States
The function of a PATHCOM command depends on the state of the object at the time you issue
the command. For example, if an object such as a server class is not configured, the START
command for that object has no effect because that object cannot be started until it is configured
using the SET and ADD commands. Figure 22 (page 126) illustrates the relationship between the
state of an object and the function of the PATHCOM commands.
Figure 22 PATHCOM Commands and Object States
NOTE: The CONTROL TERMs command must be issued when TERM is in the STOPPED state for
COUPLE request.
The relationships illustrated in Figure 22 (page 126) apply for all of the PATHCOM commands and
the PATHMON-controlled objects. Some PATHCOM commands affect only certain objects and
their operation. For example, the CONTROL command affects only the PATHMON process and the
FREEZE SERVER command affects only server classes.
NOTE: The PATHMON process reports only destination object states; it does not report transitional
states. To determine the current state of an object, use the appropriate STATUS command.
126 Overview of PATHCOM