OpenTP1 Version 7 Description

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

3.9.4 Obtaining the message log

OpenTP1 enables the editing and storing of system messages, and thereby enables the monitoring of online systems.

Figure 3-71 gives an overview of how the message log is obtained.

Figure 3-71 Obtaining a message log

[Figure]

For details about message-log operations, see the manual OpenTP1 Operation.

Organization of this subsection
(1) The OpenTP1 log service and message log files
(2) Requesting numbered messages
(3) Suppressing the message log
(4) Specifying the language for the output message log

(1) The OpenTP1 log service and message log files

The OpenTP1 log service manages system messages. For example, the log service:

The log service outputs a message to one of two message log files: dclog1 or dclog2. Using round-robin scheduling, the log service outputs messages to one of the files and when this file is full, the log service reports this fact and proceeds to output messages to the other file. The previous generation of the message log is preserved. When the second message log file is full, the log service reports this fact and proceeds to overwrite the messages in the first file. Messages that the log service outputs to a message log file are simultaneously output to the console.

You can use the command logcat to output system messages from a message log file to the standard output. OpenTP1 compares the last update times of dclog1 and dclog2 and then outputs the information in both message log files in chronological order.

(2) Requesting numbered messages

You can request that OpenTP1 assign message sequence numbers to each message in the message log files and this information can be obtained as additional message-log information. Even if an error removes a message, the missing sequence number indicates that the message is missing.

You can use options of the command logcat to specify how the message log is to be formatted.

(3) Suppressing the message log

If a lock error occurs, OpenTP1 outputs the message log. Repeated attempts to re-execute a UAP that returned an error results in increasing the size of the message log. For the DAM files, you can specify in the dam_message_level operand in the DAM service definition whether to output the messages returned by lock error. If you omit this specification, no message is output.

(4) Specifying the language for the output message log

You can choose whether to output the message log in English or in Japanese. Specify the required language in the LANG environment variable in putenv format in the system common definition. If you omit this specification, the message log is output in English.