Figure 1. Example:
CFMANAGER exception report ***** CFMANAGER EXCEPTION REPORT *****
CFMANAGER RELATED EXCEPTIONS
-----------------------------
IWM0004I Validity check failure, reason aaxxbbcc, for WLM data area
at address zzzzzzzz in ASID X'gggg'.
zzzzzzzz XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX │ ................ │
+0010 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX │ ................ │
+0020 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX │ ................ │
+0030 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX │ ................ │
+0040 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX │ ................ │
IWM0005I Validity check warning, reason aaxxbbcc, for WLM data area
at address zzzzzzzz in ASID X'gggg'.
zzzzzzzz XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX │ ................ │
+0010 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX │ ................ │
+0020 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX │ ................ │
+0030 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX │ ................ │
+0040 XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX │ ................ │
- Error/Warning control block record
- reason: aaxxbbcc
- This field contains the reason code associated with the error.
The format of the reason code is aaxxbbcc where aa is the control
block ID for the data area in error, xx is the ID of the module that
detected the error, bb is not used, and cc identifies the error detected.
The control block identifiers and modules IDs are defined in IWMZCONS.
- Control block address: zzzzzzzz
- This field contains the address of the control block in error.
The control blocks reported by the CFMANAGER exception report is
the:
- CFCT mapped by IWMCFCT,
- and CFSD mapped by IWMCFSD
- ASID: X'gggg'
- The address space identifier (ASID) in hexadecimal where the control
block exists.