Standalone Logtool for MPE/iX

455 ****** UNABLE TO COMMUNICATE WITH MEMORY LOGGING PROCESS (LTERR 455)
CAUSE The user has issued either a MEMTIMER, MEMCLR, or MEMRPT command to LOGTOOL. To perform
these commands, LOGTOOL must communicate with the memory logging process. LOGTOOL is not able to
locate MEMLOGP.
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.
456 ****** UNABLE TO OBTAIN MEMORY REPORT DATA (LTERR 456)
CAUSE The user has issued a MEMRPT command to LOGTOOL. LOGTOOL was not able to successfully obtain
memory report information from the memory logging process (MEMLOGP).
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.
457 ****** UNABLE TO START DISPLAYLOG COMMAND (LTERR 457)
CAUSE LOGTOOL was not able to notify the diagnostic system that DISPLAYLOG was to start.
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.
458 ****** UNABLE TO STOP DISPLAYLOG COMMAND (LTERR 458)
CAUSE LOGTOOL was not able to notify the diagnostic system that DISPLAYLOG was to stop.
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 generated when performing the LOGTOOL command
again.
459 ****** LOGTOOL ABORTING DUE TO AN UNRECOVERABLE ERROR. FURTHER ERROR
INFORMATION HAS BEEN LOGGED IN THE SYSTEM LOG FILE. (LTERR 459)
CAUSE LOGTOOL encountered an error it could not recover from. Further error information has been logged into the
system log file as a diagnostic log record. Depending on the error, this message may not make it to the
users terminal, but LOGTOOL is try to tell the user that it is aborting.
ACTION Please find the diagnostic log record containing the detailed error information on why LOGTOOL aborted. In
most cases, a service request may need to be submitted.
460 ****** LOGTOOL ERROR NUMBER IS !. (LTERR 460)
CAUSE LOGTOOL encountered an error it could not recover from. The number given will identify the type of error
encountered.
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 generated when performing the LOGTOOL command
again.
461 ****** LOGTOOL ABORTED DUE TO AN ERROR IN PROCEDURE ! (LTERR 461)
CAUSE LOGTOOL encountered an error it could not recover from. The procedure name given will identify the
location in LOGTOOL code where the error occurred.
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.
462 ****** UNEXPECTED ERROR OCCURRED WHILE TRYING TO CONVERT A LOG NUMBER
***TO A PASCAL STRING (LTERR 462)
CAUSE After obtaining a log number from the user, LOGTOOL needs to convert that number from an integer to a
PASCAL string. This string is later used to form a log file name.
ACTION An error message containing further information will be displayed with this message. Please refer to the