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

PATHMON Environment Control Commands
NonStop TS/MP System Management Manual—541819-001
11- 9
LOG1 and LOG2 Commands
STATUS
sends status change messages and error messages to the file you specify with
file-name. If the STATUS option is not specified, only error messages are
written to the log file.
EVENTFORMAT
specifies that messages should be formatted as event messages. If you omit
EVENTFORMAT, text messages are generated.
Considerations
•
The OUT file initially specified with the PATHMON RUN command becomes the
initial LOG1 file until you specify otherwise by issuing a logging command. The file
is opened when you specify the STATUS attribute.
•
It is better to specify a disk file for logging than a terminal because log messages
are lost once they scroll off the terminal screen. Also, performance is generally
better to a disk file than to a terminal.
If the logging file is a terminal, it is best to use that terminal only for logging. If that
is not possible, restrict the activity on that terminal to avoid interfering with
messages from the PATHMON process. In either case, type “pause” at the TACL
prompt to suspend the TACL process so that logging can occur.
•
EDIT files are not acceptable log files to the PATHMON process. If you attempt to
use an EDIT file for a log, the PATHMON process returns an error and fails to
open the log.
•
If a logging command is used with no attributes, the corresponding log file is
closed.
•
Logging of status messages is automatically disabled during execution of the
SHUTDOWN2 command.
Examples
This command sends error information to a terminal:
LOG1 $TERM1
This command logs errors and status change messages in a file named COMPLOG:
LOG2 COMPLOG,STATUS
This command logs errors and status change messages to $0, and formats the
messages as event messages:
LOG1 $0, EVENTFORMAT, STATUS
Note. If a logging terminal is unavailable, the PATHMON environment may slow down and
be unable to support transaction processing.