This message is the format of database error messages that are displayed as a WTO. Some of these messages, called noncrux messages, contain RC=xx REAS=yy. Others, called crux messages, do not contain RC=xx REAS=yy. A crux message is the first message to appear when a problem occurs. As the system backs out to successively higher logic levels, other messages that are related to the problem occur. These messages display the return codes and reason codes that they received from the lower level.
The unique message number. This is the primary sequence of the following messages. The following conventions have been observed in the numbering of the system messages:
Common messages issued within all modules.
Messages issued within functional modules.
Messages issued within subroutine modules.
Messages issued within environment modules.
Messages issued on return from external routines.
Messages issued on return from functional modules.
Messages issued on return from subroutine modules.
Messages issued on return from environment modules.
Severity indicator. Contains one of the following values:
Information
Warning
Error
The last four characters of the module name (for example, V0A0).
Displacement within the module issuing the error message.
Return code displayed only for noncrux messages. Contains one of the following:
Warning.
Error encountered, processing cannot continue.
Error encountered, system cannot recover.
Reason code displayed only for noncrux messages.
A brief description of the problem encountered.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|