DFS550I DFSNDMI0 {SUCCEEDED|FAILED} REGION=rrrrr JOBNAME=jjjjjjjj STEPNAME=ssssssss TRANSACTION=tttttttt PSB=pppppppp SSYSID=wwwww[FAILURE CODE=xxx RETURN CODE=yyy|N/A] [DESTINATION=dddddddd DSYSID=zzzzz|N/A] timestamp
Explanation
The application program associated with PSB pppppppp terminated abnormally while processing transaction tttttttt. The Non-Discardable Messages User exit interface (DFSNDMI0) either succeeded or failed in requeuing the input message associated with transaction tttttttt to destination dddddddd.
If DFSNDMI0 succeeded, the DESTINATION and DSYSID= information are displayed. The FAILURE CODE information and the RETURN CODE information are not displayed.
If DFSNDMI0 failed, the FAILURE CODE and the RETURN CODE information are displayed. The DESTINATION and DSYSID information are displayed only for some failure codes. If displayed, the DESTINATION and DSYSID information follow the FAILURE CODE information and the RETURN CODE information.
The SUCCEEDED version of this message is always followed by message DFS554A, and for certain conditions, can also be followed by DFS555I. The SUCCEEDED version is issued only if DFSNDMI0 successfully queues the input message associated with transaction tttttttt to destination dddddddd after receiving return code 16 from the Non-Discardable Messages user exit NDMX.
- rrrrr
- Region ID
- jjjjjjjj
- Job name (padded with blanks)
- ssssssss
- Step name (padded with blanks)
- tttttttt
- Transaction that the application associated with PSB pppppppp was processing when it abended
- pppppppp
- PSB associated with abended application program
- wwwww
- System ID of the system from which the input message in process and associated with transaction tttttttt originated (the source system ID)
- xxx
- One of the following failure codes is displayed only in the FAILED
version of this message:
- 001
- Queue manager was unable to obtain the input message associated with transaction tttttttt.
- 002
- Unable to obtain storage for NDM SPA buffer (IMODULE GETSTOR failure).
- 003
- Unable to obtain storage for message segment buffer (IMODULE GETSTOR failure).
- 004
- There is no input message.
- 005
- OTMA FINDDEST failed.
- 006
- System locate service failed (DFSSLC failure).
- 007
- FINDDEST failed (DFSFNDST failure).
- 008
- LUM failed to build the APPC message prefix.
- 009
- Queue manager failed to insert the message.
- 010
- No more inserts are allowed by this UOW.
- 011
- The Non-Discardable Messages user exit specified an invalid destination transaction for requeue.
- 012
- The message was not requeued to its permanent destination (DFSICLR2 failure).
- 013
- Unable to obtain storage for the NDM interface block (IMODULE GETSTOR failure).
- 014
- Unable to obtain storage for the USRX interface block (IMODULE GETSTOR failure).
- 015
- The Non-Discardable Messages user exit was not started (DFSUSRX failure).
- 016
- The destination specified for requeue is zeros or blanks (return code 16 from the Non-Discardable Messages user exit).
- 017
- Unable to obtain storage for message record buffer (IMODULE GETSTOR failure).
- 018
- Unable to obtain storage for single segment message buffer (IMODULE GETSTOR failure).
- 019
- The Non-Discardable Messages user
exit requested that IMS requeue the input message to
a transaction. However, one of the following conditions exists:
- One of the input message segments exceeds the allowable segment length for the destination transaction.
- The total number of input message segments exceeds the allowable number of segments for the destination transaction.
- yyy
- Return code of the IMS service that failed, or N/A if xxx is 004, 010, 011, 016, or 019. This field is displayed only in the FAILED version of this message.
- dddddddd
- Destination to which the Non-Discardable Messages user exit asked to have the input message requeued (return code 16). This field is always displayed in the SUCCEEDED version of this message; it is sometimes displayed in the FAILED version of this message.
- zzzzz
- Destination system ID – system ID of the system to which the input message in process and associated with transaction tttttttt was sent (SUCCEEDED version) or would have been sent (FAILED version), or N/A if xxx = 005, 006, or 007. This field is always displayed in the SUCCEEDED version of this message; it is sometimes displayed in the FAILED version of this message.
System action
For the SUCCEEDED version of this message, the input message associated with transaction tttttttt is requeued to destination dddddddd and then deleted from transaction tttttttt. For the FAILED version of this message, the input message associated with transaction tttttttt is deleted from the system unless the application abend is 3303, 2478, 0777, or 2479.