DFS554A jobname.region.stepname. prog PSBname(x)
transaction-code
sys-completion-code user-completion-code
PSB SMB
LTERM:|LUNAME:|RTKN=token
REASON=reason originating terminal
Explanation
The IMS application indicated by prog PSBname encountered a system abend or a user abend indicated by sys-completion-code or user-completion-code respectively.
The information for this message is printed as indicated. This message can be multiline.
The program PSB name is associated with one of the following region types, which is indicated by (x):
- 0
- IMS program controller
- 1
- MPP region
- 2
- BMP region
- 3
- The Coordinator Control (CCTL) thread
- 4
- IFP region
- 5
- JMP region
- 6
- JBP region
- 7
- Application Execution Region (AER) region; for example, an ODBM application that is running in an AER
- (x)
- Identifies the region type associated with the job name.
- For an MPP region, x = 1.
- For a BMP region, x = 2.
- For a DBCTL region, x = 3.
- For an IFP region, x = 4.
- For a JMP region, x = 5.
- For a JBP region, x = 6.
- For an AER region, x = 7.
- A CCTL application abend or pseudoabend
- A CCTL abend
- A CCTL request for termination of its connection to DBCTL while its thread is still active
SMB indicates that the transaction was stopped, and the absence of SMB indicates that the transaction was not stopped. PSB indicates that the program was stopped, and the absence of PSB indicates that the program was not stopped. LTERM or LUNAME is the name of the terminal. LUNAME is displayed in place of LTERM when the originating terminal is LU6.2 or OTMA, unless the LUNAME information is in transition. If the LUNAME information is in transition, UNKNOWN is displayed.
For DBCTL/CCTL threads, this message displays the recovery token. The first 8 bytes of this token are in EBCDIC and are displayed as characters; the second 8 bytes of the token are displayed in hexadecimal form. However, if DBCTL detects a failure during scheduling of the PSB (for example, abends 0428, 0437, 0456, 0457, and 0458), the recovery token is displayed as zeros. This signifies that recovery of an unscheduled PSB is not needed.
Except for DBCTL, if the user completion code is U428, the PSB name is blank because the PSB was not found.
If the user completion code is 0448, 0452, 0456, or 0458, the transaction code and the stopped SMB name are blank.
If the user completion code is 0464, SYS does not represent a system completion code, but rather the error return code from the reply SVC. These return codes are:
- Codes
- Explanation
- 001
- Simulated region termination or reply recursion.
- 002
- Address of the dependent region TCB is invalid.
- 003
- Dependent task is terminating (TCBFLGS1 is set).
- 004
- Dependent task is terminating (TCBFLGS5 is set).
- 005
- Dependent task does not have an RCPARMS.
- 006
- PSTID does not match RCID.
- 009
- The dependent region was probably canceled by z/OS®.
REASON=reason is displayed only if the abend reason code is available. The message can be issued during Create Thread processing or by the dependent region environment controller module (for example, DFSECP10). reason has the following forms:
- For abend 0711
- REASON=xxxxyyyy, where xxxx is the return code from z/OS Recovery Resource Management Services (RRMS) or from z/OS UNIX System Services, and yyyy is the abend 0711 reason code.
- For abend 0129
- REASON=xxxxyyyy, where xxxx is the SAF return code and yyyy is the RACF® or equivalent return code.
- For abend 0128
- REASON=xxxxxxxx, where xxxxxxxx is the return code from the APPC Associate service (ATBASOC).
- For abend 0109
- REASON=xxxxxxxx, where xxxxxxxx is the return code from the APPC/OTMA synchronous shared queue.
- For abend 0425
- REASON=xxxxxxxx in the DFS554A message identifies the reason code or completion code of why the runtime program resource or runtime database resource could not be created. Refer to DFSCMDRR for the explanation of the reason code or completion code.
- For abend 0426
- REASON=xxxxxxxx in the DFS554A message identifies the reason code or completion code of why the runtime program resource or runtime database resource could not be created. Refer to DFSCMDRR for the explanation of the reason code or completion code.
System action
availableif the input message in process by the application is on the message queue. Exceptions are:
- The application has not issued a GU call. Therefore, the message did not cause the abnormal termination.
- An abnormal termination that could be rescheduled occurred (for example, PI lockout) unless the Non-Discardable Messages user exit told IMS to discard the input message.
- This message is preceded by the SUCCEEDED version of message DFS550I.
The preceding exceptions allow the message to run again.
If the application program terminated abnormally after the last message was removed from the applicable queue, the transaction is not available and only message DFS554A is printed.
If during
the initialization of a new message region the IMS control region can determine that a previous
region was canceled, the job name and step name fields of this message
contain the words REGION CANCELED. The region is
the identity of the new dependent region.
If a system abend 806 occurs in a persistent JVM dependent region, this message might follow message DFS480E.
If DFS554A displays Language Environment abend U4088 with return code 63, verify that the save area passed into IMS is correct. In IMS modules DFSTMPR0, DFSPCC20, DBFFPPR0, or DFSESPR0, this abend is likely produced by the CEEVGTUN call within the module, and indicates a problem with the save area. To learn more, see the description for return code X’63' (99) in Language Environment abend code U4088 (X'FF8’).
Operator response
(master terminal) Inform appropriate personnel of the application program abend. See abends 0448, 0452, 0456, 0458. See message DFS550I which might precede this message at the IMS master terminal.Programmer response
Correct the cause of the application program abend.