TS/MP System Management Manual (H06.05+, J06.03+)

Maintaining a PATHMON Environment
HP NonStop TS/MP System Management Manual—541819-007
5-23
Logging Status and Error Information
This step completes your configuration and start operations.
If you frequently alter your global configuration, using the OBEYFORM option to create
a command file can be helpful.
Logging Status and Error Information
PATHMON reports error and status information to a log file.
You can request the PATHMON process to report errors only, or errors and changes in
object status as well. You can request the PATHMON process to log information to
only one file, or to copy the information to two files. Also, you can request that error
and status information be formatted either as text or as tokenized event messages
(managed by the Event Management Service (EMS) portion of the Distributed Systems
Management (DSM) software).
You can log information to a command terminal or to a disk file; it is recommended,
however, that you not specify a terminal. On a terminal, log messages are lost once
they scroll off the terminal screen; also, performance is generally better to a process on
a disk file than to a terminal.
Security Logging
The TS/MP 2.4 PATHMON makes a log entry for the following commands when they
are issued on the objects configured under PATHMON:
•
ABORT
•
ADD
•
ALTER
•
DELETE
•
FREEZE
•
STOP
•
THAW
•
START
Note. OBEYFORM presents certain limitations. First, it produces a highly restrictive record of
your system configuration, one in which the default values recorded are those assigned by the
current version of the PATHMON environment. The file names recorded are fully expanded on
the basis of current file assignments at your node. In addition, OBEYFORM produces files that
contain values for all object attributes, whether assigned by a PATHCOM command or by
default.