Standalone Logtool for MPE/iX

this situation, it was not able to successfully perform that task.
ACTION An error message containing further information will be displayed with this message. Please refer to the
ACTION clause of that error message for further information.
502 ****** INVALID LOG RECORD TYPE ! RECORD SKIPPED (LTWARN 502)
CAUSE LOGTOOL encountered a log record with an invalid record type. This log record will be skipped and will not
appear in the report.
ACTION Please submit a service request indicating the following:
a) The exact text of the above error message including the parameter.
b) Any other error messages displayed with this error message.
c) The sequence of LOGTOOL commands which were being performed when this error message was
encountered.
d) The version (A.nn.nn) of the LOGTOOL being executed.
503 ****** USER INTERRUPTS COULD NOT BE ENABLED. (LTWARN 503)
CAUSE LOGTOOL will not be able to enable user interrupts (CONTROL-Y for MPE/iX) during initialization.
LOGTOOL will execute, but user interrupts will be ignored.
ACTION Enable error tracing by rerunning the program with the TRACE=ERROR parameter at the DUI command
line, and file a service request with the trace information.
506 ****** LAYOUT FILE EMPTY OR HAS FEWER RECORDS THAN HEADER SAYS.
***(LTWARN 506)
CAUSE LOGTOOL has encountered an unexpected end of file while reading its data base file LAYOUTF.
ACTION Contact support personnel to get new LAYOUTF and LAYMSG files.
507 ****** NO LAYOUT ENTRY FOR LOG TYPE ! WITH VALUE ! (LTWARN 507)
CAUSE During the generation of a log report, LOGTOOL was not able to locate a "TAG" definition for the log record
type indicated.
ACTION Since LOGTOOL cannot find the definition, the data will be displayed as a HEX dump, and the report will
continue.
508 ****** NO VALUE LABEL FOR LOG TYPE ! [VALUE= !] (LTWARN 508)
CAUSE During the generation of a log report, LOGTOOL was not able to locate a "TAG" definition for the log record
type indicated.
ACTION Since LOGTOOL cannot find the definition, the data will be displayed as a HEX dump, and the report will
continue.
510 ****** STRING IN A LOG TYPE ! WITH LENGTH ! IS LARGER THAN MAX SIZE
***IN LAYOUT (SKIPPING DECODE OF THIS FIELD). (LTWARN 510)
CAUSE During the generation of a log report, LOGTOOL encountered a string to be displayed which was larger that
the buffer allocated within LOGTOOL.
ACTION Please submit a service request indicating the following:
a) The exact text of the above error message including the parameters.
b) Any other error messages displayed with this error message.
c) The version (A.nn.nn) of the LOGTOOL being executed.
A copy of the log file containing the log record producing this error should also be submitted with the
service request.
512 ****** CONSOLE TEXT LENGTH OF ! IS INVALID. TEXT NOT DISPLAYED (LTWARN 512)
CAUSE LOGTOOL was not able do display the console logging record because the text was larger that the buffer
allocated within LOGTOOL.
ACTION Please submit a service request indicating the following:
a) The exact text of the above error message including the parameters.
b) Any other error messages displayed with this error message.