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

Maintaining Pathway/iTS Objects
HP NonStop Pathway/iTS System Management Manual—426748-002
4-18
Using EMS Event Messages
From this information, the operator sees that two TERM objects are not running. The
error codes under the ERROR and INFO columns help solve the problem. Error code
3017 is a PATHMON error that can be displayed with the HELP command:
= HELP 3017
PATHTCP ERROR - *3017* ERROR DURING TERMINAL OPEN
Error code 14 is a file-system error that can be displayed with the TACL ERROR
command:
11> ERROR 14
014 device does not exist
From these error codes, the operator determines that the file names of the devices
associated with the TERM objects do not exist. To change the device file names for the
TERM objects, these commands are used:
= ABORT TERM *, STATE SUSPENDED
TERM-1-2, STOPPED
TERM-4-5, STOPPED
= ALTER TERM-1-2, FILE $TTB.X56
= ALTER TERM-4-5, FILE $TTB.X70
= START TERM *
TERM-1-2, STARTED
TERM-4-5, STARTED
As a final check, STATUS TERM is used again:
= STATUS TERM *, STATE NOT RUNNING
=
Because no information is returned from the command, the operator knows that all
TERM objects are running.
Using EMS Event Messages
Event messages for TCP and TERM objects are an important source of detecting
exception conditions for these objects. Because of the large quantity of events often
generated, it is not easy or efficient for an operator to read the event message log to
detect certain exception conditions.
As an alternative to having an operator read the event messages, you can:
•
Use an EMS printing distributor with filtering logic to sort out the messages the
operator should take immediate action on.
For more information about printing distributors and filters, see the EMS Manual.
•
Develop an SPI process to monitor the event messages for exception conditions to
take action on.
This process can be designed to determine the cause of the problem, based on the
event message, and then report the condition to the operator, along with corrective
action to take.