Job Formatter Format

The messages sent for log entries that were not supported prior to level 2.0 of the interface software are always sent in Job Formatter format. Messages for log entries that were supported prior to level 2.0 are sent in Job Formatter format only if

The filter file contains the option LOG_COMPATIBILITY 2 on the line that specifies the log type (see Section 3), or
The log type was added with a FILTER ADD command that includes the option LOG_COMPATIBILITY 2. See Section 5.

See 6.3.2 for a list of log entries that were supported prior to level 2.0.

The format of Job Formatter messages is:

jobnum/taskum TYPE:major,minor hhmmss specific-text

where:

jobnum

is the job number of the MCP process associated with the log entry.

taskum

is the task number of the MCP process associated with the log entry.

major,minor

is the major, minor type of the log entry.

hhmmss

is the time at which the log entry was made.

specific-text

is the text specific to the log entry. See the System Log Programming Reference Manual for format of the text specific to each log entry.

If the total length of the message sent to Operations Sentinel is more than 1024 characters, including the prefix, the message is truncated to 1,000 characters, and the following 22 characters, plus 2 spaces before the T, are appended:

TRUNCATED:LEN=bbbbbbbb

where bbbbbbbb is either the full length of the formatted log entry in bytes or, for very large log entries, the raw log record size. The cutoff for very large log entries is approximately 6,000 bytes.

When using Job Formatter format (LOG_COMPATIBILITY 2) with major/minor 6.3,the MCP Operations Sentinel agent will send all 6,3 events to the Operations Sentinel server instead of the limited entries sent when using classic mode.

For example, when using Job Formatter mode for 6,3, the Operations Sentinel log will include the responses to waiting entries.