OpenTP1 Version 7 Operation

[Contents][Index][Back][Next]

3.6.1 Message log

The following two facilities are used to monitor the online status:

Organization of this subsection
(1) Realtime output facility
(2) Output to message log file and editing

(1) Realtime output facility

Message logs output to the message log file can be output in realtime to the standard output. To do this, log_msg_console=Y must be specified in the log service definition. The user can also specify whether or not the message serial numbers, request source process IDs, output request dates and times, etc., are to be output.

The log_msg_console specification can be changed in the online mode with the logcon command.

(2) Output to message log file and editing

(a) Output to message log file

OpenTP1 outputs a message log to the message log file upon receipt of an output request from each system service, MCF, or UAP.

The two message log files are $DCDIR/spool/dclog1 and $DCDIR/spool/dclog2. These two files are used with the round-robin scheduling method, and the immediately preceding generation of the message information is guaranteed. When the files are switched, a message to that effect is displayed. If a file needs to be saved, the user must back it up before new information is overwritten into it.

(b) Message log editing and output

The messages in the message log files can be output to the standard output by executing the logcat command. The messages in the two message log files, $DCDIR/spool/dclog1 and $DCDIR/spool/dclog2, are merged and then output in chronological order.

(c) Cautions about the amount of log output

If there is a large amount of log output, any of the following failures may occur. When operating OpenTP1, care should be taken to prevent the amount of output messages from extremely increasing if a failure occurs.