Pathway/iTS System Management Manual (G06.24+)

HP NonStop Pathway/iTS System Management Manual—426748-002
7-1
7 Overview of PATHCOM
This section contains overview information to help you get started using PATHCOM to
manage HP NonStop Pathway/iTS objects in your PATHMON environment. See the
TS/MP System Management Manual for more detailed information on how PATHCOM
works, how to manage your PATHMON environment, and how to configure and
manage the TS/MP objects.
PATHCOM Interface to PATHMON
Environments
PATHCOM is a command language interpreter and interactive command interface to
the PATHMON process. Using PATHCOM, which consists of sets of object-related
commands, you can interactively define and manage all objects that can be controlled
by the PATHMON process.
Some commands are processed directly by PATHCOM; others are processed by the
PATHMON process, and one or more TCP or LINKMON processes might be involved
in the execution of those commands. The commands described in this manual, which
define, start, and stop objects controlled by the PATHMON process, are passed to the
PATHMON process by PATHCOM.
PATHMON-Controlled Objects
An object is an entity that you can see and control interactively by using PATHCOM or
programmatically by using a management application that you write for the Pathway
management programming interface. Each object type performs a specific function
within a Pathway environment. The set of objects configured and controlled by the
PATHMON process are referred to in this manual as the PATHMON environment or the
PATHMON-controlled objects. The PATHMON-controlled objects that support
requesters are the TCP, TERM, PROGRAM, and TELL objects, introduced in
Section 1, Introduction to Pathway/iTS System Management
, and discussed
throughout this manual. The PATHMON-controlled objects that support servers and the
overall Pathway and PATHMON environments are the SERVER, PATHWAY, and
PATHMON objects, respectively, also introduced briefly in Section 1. For a description
of the SERVER, PATHWAY, and PATHMON objects, and a discussion of how requester
and server objects interrelate, see the TS/MP System Management Manual.
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 TCP is not configured, the
START command for that object has no effect because that object cannot be started
until it is configured using the ADD command. Figure 7-1 on page 7-2 illustrates the
relationship between the state of an object and the function of the PATHCOM
commands.