TS/MP System Management Manual (G06.24+, H06.03+)

Maintaining a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
5-24
Logging Information to a Disk File
Logging Information to a Disk File
To select a destination other than your terminal for logging information, you can enter a
run option with the implicit RUN PATHMON command, as follows:
5> PATHMON / NAME $PMX, CPU 3, NOWAIT, OUT LOGPMON/
Alternatively, you can specify the file for logging output by using the PATHCOM
commands LOG1 and LOG2. For example, to specify $0 as the log file for errors
reported in tokenized event message format, and to specify the disk file LOGCOPY as
a log file for both error and status change information in text format, enter:
= LOG1 $0, EVENTFORMAT
= LOG2 LOGCOPY, STATUS
Before specifying a disk file for logging, you must first create that file, using the FUP
CREATE command. (You should ensure that the file is large enough.)
The PATHMON process records the log file names that you select in the PATHMON
configuration file. After a cool start, the same log files specified in the configuration file
are used again; records produced after the cool start are appended to these files.
If an error occurs while error information, status information, or both are being written
to a log file, the PATHMON process does:
1. Closes the log file specified with the file-name parameter.
2. Opens $0.
3. Writes the information to $0. The PATHMON process writes error information,
status information, or both to $0, depending on what was specified for the initial log
file with the STATUS parameter. Additionally, the PATHMON process writes the
information to $0 in the same format (that is, event messages or text) specified for
the initial log file with the EVENTFORMAT parameter.
If an error then occurs while information is being written to $0, the PATHMON process
closes $0 and prohibits further error and status logging. The PATHMON process does
not reopen either the log file or $0.
In this example, you have configured two log files:
= LOG1 $0, EVENTFORMAT
= LOG2 $DATA.PM.LOGFILE, STATUS
If an error occurs on LOG1, the PATHMON process closes the log because the error
occurred on $0; the PATHMON process would not reopen LOG1. If an error occurs on
LOG2, the PATHMON process reopens $DATA.PM.LOGFILE as LOG2 $0, STATUS.
The PATHMON process next sends both error information and status information to $0
because although the LOG1 command did not specify the STATUS parameter, the
LOG2 command did. Additionally, the PATHMON process sends both event