Interpreting return codes from IEFDB476
- Message processing reason code (S99ERCO)
- Message block freeing reason code (S99ERCF)
- PUTLINE/WTO macro return code (S99EWRC).
- Hexadecimal Return Code
- Meaning and Action
- 00
- Meaning: The request is successful.
Application Programmer Action: None required.
- 04
- Meaning: The identification number of
the caller is invalid
Application Programmer Action: Correct the value supplied in the EMPARMS field EMIDNUM and resubmit the request. Valid values are described in Caller identification number (EMIDNUM).
- 08
- Meaning: An error occurred in PUTLINE
or WTO while issuing a message. The PUTLINE or WTO return code, if
any, is in the S99EWRC field of the request block extension.
Application Programmer Action: If a request block extension was supplied, the field S99ERCO contains a reason code. See Message processing reason code (S99ERCO) for the appropriate action for that reason code.
If no RBX was supplied, see the descriptions of reason codes 03, 04, 06, and 07 in Message processing reason code (S99ERCO) for possible causes and actions to take for this error.
- 0C
- Meaning: The IEFDB476 program is unable
to return messages for one of the following reasons:
- A request block extension (RBX) was supplied, but the RBX field
S99ENMSG contains 0, indicating that the dynamic allocation request
did not return messages. The dynamic allocation request might not
have returned messages because:
- The request was successful, and no messages were returned. The
RBX field S99ERCO contains a reason code of 0D.
Application Programmer Action: See the description of reason code 0D in Message processing reason code (S99ERCO) for the appropriate action.
- o The request was unsuccessful but no messages were returned.
The reason is unknown. The RBX field S99ERCO contains a reason code
of 0B.
Application Programmer Action: See the description of reason code 0B in Message processing reason code (S99ERCO) for the appropriate action.
- Bit S99ERMSG in the RBX was not set on to request that the system
return messages in the message block. The RBX field S99ERCO contains
a reason code of 0C.
Application Programmer Action: See the description of reason code 0C in Message processing reason code (S99ERCO) for the appropriate action.
- The request was successful, and no messages were returned. The
RBX field S99ERCO contains a reason code of 0D.
- The RBX supplied to the IEFDB476 program was not valid.
Application Programmer Action: Verify that the RBX being supplied to IEFDB476 is the correct RBX and has not been modified.
- Message extraction was requested through bit EMRETURN in the EMFUNCT
field, but no message buffer address was supplied. The RBX field S99ERCO
contains a reason code of 0A.
Application Programmer Action: See the description of reason code 0A in Message processing reason code (S99ERCO) for the appropriate action.
- An RBX was supplied but the message block chain was not valid.
The RBX field S99ERCO contains a reason code of 09.
Application Programmer Action: See the description of reason code 09 in Message processing reason code (S99ERCO) for the appropriate action.
- A request block extension (RBX) was supplied, but the RBX field
S99ENMSG contains 0, indicating that the dynamic allocation request
did not return messages. The dynamic allocation request might not
have returned messages because:
- 10
- Meaning: The IEFDB476 program is unable
to free the storage associated with the message block chained out
of the request block extension. Hexadecimal return code 10 applies
only to DYNALLOC callers that have a request block extension.
Application Programmer Action: The S99ERCF field in the request block extension contains a reason code. Take the action described for that reason code in Message block freeing reason code (S99ERCF).