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

Maintaining Pathway/iTS Objects
HP NonStop Pathway/iTS System Management Manual—426748-002
4-17
Managing Exception Conditions
For instructions on specifying a destination for TCP error and status messages, see
the TS/MP System Management Manual.
Managing Exception Conditions
You can change various aspects of a PATHMON environment as it is running. Often
you will need to change system parameters because an exception or error condition
has occurred for an object, such as a TERM object or TCP. Before you can respond to
an exception condition, you must know that the condition exists and what caused it.
There are two ways to detect an exception condition for a TERM object or TCP:
•
Periodically check the object’s status with a STATUS TERM or STATUS TCP
command.
•
Monitor the log file for TERM and TCP information. When it fails, a TCP generates
an EMS 512 event (old format), regardless of the system configuration.
You might need to use both methods to detect the conditions you are interested in
because not all exception conditions show up in both sources.
Using PATHCOM Commands
The PATHCOM commands can be issued by an operator on a regular basis to check
exception conditions for TERM objects and TCPs. Or, you can develop an SPI process
to issue the commands, determine if a problem exists, alert the operator to the
problem, and provide corrective action to take. (Several third-party companies also
provide such SPI processes.)
The following examples use PATHCOM commands. For additional information on
using PATHCOM commands to monitor your system, see the TS/MP System
Management Manual. For more information about SPI processes to manage the
TS/MP and Pathway/iTS products, see the TS/MP Management Programming Manual
and the Pathway/iTS Management Programming Manual.
As an example of an operator using the PATHCOM commands, assume an operator
checks to determine if any of the TERM objects are not running after the environment
is started. The operator enters this command:
= STATUS TERM *, STATE NOT RUNNING
The STATUS command returns this information:
TERM STATE ERROR INFO TCP FILE
TERM-1-2 SUSPENDED 3017 14 TCP-2 \SKY.$TT2.X33
TERM-4-5 SUSPENDED 3017 14 TCP-5 \SKY.$TT5.X45