The following is an example of the ERROR field from the sample SYSEVENT file that is shown in Figure 3. Table 1 describes the ERROR identifiers.
ERROR 0 1 0 0 3 3 0 0 CCNnnnn E 12 26 Undeclared identifier add.
A B C D E F G H I J K L M
Column | Identifier | Description |
---|---|---|
A | Revision | Revision number of the event record. |
B | File number | Increments starting with 1 for the primary file. |
C | Reserved | Do not build a dependency on this identifier. It is reserved for future use. |
D | Reserved | Do not build a dependency on this identifier. It is reserved for future use. |
E | Starting line number | The source line number for which the message was issued. A value of 0 indicates the message was not associated with a line number. |
F | Starting column number | The column number or position within the source line for which the message was issued. A value of 0 indicates the message was not associated with a line number. |
G | Reserved | Do not build a dependency on this identifier. It is reserved for future use. |
H | Reserved | Do not build a dependency on this identifier. It is reserved for future use. |
I | Message identifier | String Containing the message identifier. |
J | Message severity character |
|
K | Message severity number | Return code associated with the message. |
L | Message length | Length of message text. |
M | Message text | String containing message text. |