0100/0110
(X’100’/X’110’, decimal:
256/272)
Explanation
The synchronous program switch request failed. The exact cause depends on the extended reason code value.
| Extended reason code | Description |
|---|---|
| X'0000' | The request message was rejected because the specified transaction is not supported. Either the trancode was not found or the specified transaction was an IMS conversational transaction, a CPIC transaction, or an IMS command transaction. |
| X'0004' | The request message was rejected because the user is not authorized to issue a synchronous program switch request. |
| X'0005' | The request message was rejected because the tmember that IMS uses to process synchronous program switch requests (DFSYICAL) is stopped. Issue the command /START TMEMBER DFSYICAL to resolve the problem. |
| X'0006' | The request message was rejected because the tpipe that IMS uses to process synchronous program switch requests (DFSTPIPE of the OTMA tmember DFSYICAL) is stopped. Issue the command /START TMEMBER DFSYICAL TPIPE DFSTPIPE to resolve the problem. |
| X'000D' | The request message was rejected because IMS failed to get an internal storage YTIB to process the message. |
| X'000E' | The request message was rejected because IMS failed to activate DFSYTIB0 to process the message. |
| X'0010' | The TMEMBER or TPIPE name for late response message routing is invalid because it contains invalid characters. Check the destination descriptor. |
| X'0011' | The TMEMBER or TPIPE name for late response message routing is missing from the destination descriptor. If either value is specified, both must be included. |
| X'0012' | The TMEMBER or TPIPE name for late response message routing is incorrect. Check the destination descriptor. |
| X'0013' | The SMEM and SYNCTP parameters are mutually exclusive. |
| X'0014' | The TPIPE name for late message processing is either missing or invalid in the destination descriptor. |
| X'0015' | The request message was rejected because the request was made in a shared queues environment with different IMS MINVERS values. The IMS systems in the shared queues group must have the MINVERS value 13.1. |
| X'0016' | The request is rejected due to an OTMA global message flood condition. Too many OTMA message blocks (TIB) were allocated in the system. |
| X'0020' | The request message was rejected because the input data length is incorrect. The length of the segment must match the LLZZ value that is specified on the request. The total length of all segments in the request must match the AIBOALEN value in the AIB. |
| X'0030' | The request message was rejected because the transaction is unavailable. |
| X'0031' | The request message was rejected because the transaction is stopped. |
| X'0033' | The request message was rejected because the destination name for the program switch is an RCNT. |
| X'0034' | The request message was rejected because the destination name for the program switch is a CNT. |
| X'0035' | The request message was rejected because the destination transaction can accept only a single input segment. Multiple input segments were specified for the request. |
| X'0036' | The request message was rejected because an IMS queue manager encountered an insert error. |
| X'0037' | The request message was rejected because an IMS queue manager encountered an internal error. |
| X'0038' | The request message was rejected because a queue overflow was detected. |
| X'0039' | The request message was rejected because IMS failed to process the Fast Path transaction. |
| X'003A' | The request message was rejected because IMS queue manager failed to update the message prefix. |
| X'003B' | The request message was rejected because IMS failed to enqueue the transaction. |
| X'0060' | The request message was rejected because the synchronous program switch was canceled before a reply was received. |
| X'0061' | The request message was rejected because the target transaction does not reply to the IOPCB and does not perform a program-to-program switch. The ICAL is rejected to avoid a timeout. This rejection occurs when the REPLYCHK descriptor is set to YES for the destination transaction. If there is an asynchronous response for the ICAL, you can set REPLYCHK to NO and this ICAL is treated as valid. |
| X'0070' | IMS failed to process the response message for the synchronous program switch ICAL call. The length of an output message segment was greater than the 32K limit. |
| X'0071' | IMS failed to process the response message for the synchronous program switch ICAL call. IMS is running out of LUMP storage space to process the response message. |
| X'0072' | IMS failed to process the response message for the synchronous program switch ICAL call. IMS failed to allocate storage from subpool 231, which is required to process the response message. |
Programmer response
Take the appropriate action depending on the returned extended reason code value.
Source
DL/I codes