Reason codes for response: RETRYABLE

201
NO_CICS_IRC_STARTED
Explanation:

An Initialize_User command has been issued on an MVS™ image that has had no IRC activity since the previous IPL, and the external CICS® interface cannot determine the CICS SVC number.

System action:

The Initialize_User call fails, and the external CICS interface invokes the user-replaceable module, DFHXCURM.

User response:

Ensure that a CICS region in the MVS image has logged on to IRC (that is, has started up with the system initialization parameter IRCSTRT=YES or has started IRC dynamically with an OPEN IRC command). Alternatively, if there is no local CICS region in the MVS image, you must specify the SVC parameter that the external CICS interface is to use, by coding a CICSSVC parameter in the DFHXCOPT table. This situation can occur if you are using XCF to communicate to a CICS region in another MVS image. Once the problem has been resolved, re-issue the Initialize_User request.

202
NO_PIPE
Explanation:

An attempt has been made to open a pipe, but the target CICS system associated with the pipe has no free receive sessions.

System action:

The Open_pipe call fails, and the external CICS interface invokes the user-replaceable module, DFHXCURM.

User response:

This situation can occur even if the client application program has allocated (using Allocate_Pipe calls) no more pipes than the number of receive sessions defined on the target connection. This is because CICS can be in the process of cleaning up a pipe from a Close_Pipe request. For this reason, you are recommended to specify a larger RECEIVECOUNT value than is theoretically necessary when defining the SESSIONS resource definition to CICS. The application program can reissue the Open_Pipe request.

203 (on Open_Pipe call)
NO_CICS
Explanation:

An attempt has been made to open a pipe but the target CICS system is not available, or hasn't yet opened IRC, or the target connection is out of service, or the relevant EXCI connection definition is not installed in the target CICS.

System action:

The open pipe request fails, and the external CICS interface invokes the user-replaceable module, DFHXCURM.

User response:

If subreason field-1 is non-zero (the IRP response code (R15)), subreason field-2 contains the IRP reason code. For an explanation of the IRP return codes, see the interregion control blocks in the the CICS Data Areas manual. The IRP return codes are in the DFHIRSPS copybook, listed under the heading IRC.

When you have corrected the problem, your client application program can reissue the Open_Pipe call.

204
WRONG_MVS_FOR_RRMS
Explanation:

A DPL request omitting the SYNCONRETURN option has been made specifying a CICS region that is on a different MVS system from the batch program. Because the Recoverable Resource Management Services (RRMS) context is not recognised in the target system, the request is rejected.

System action:

The DPL request fails, and the external CICS interface invokes the user-replacable module, DFHXCURM.

User response:

Ensure that the batch program that issued the DPL request and the CICS region it was sent to are on the same MVS system.

205
RRMS_NOT_AVAILABLE
Explanation:

A DPL request omitting the SYNCONRETURN option has been made when the Resource Recovery Services (RRS) is not available. There are two cases:

- -

Note:
RRS is a part of Recoverable Resource Management Services (RRMS).
System action:

The DPL request fails, and the external CICS interface invokes the user-replacable module, DFHXCURM.

User response:

Retry the DPL request when Resource Recovery Services has restarted since the last DPL request omitting the SYNCONRETURN option, and there has been no intervening syncpoint.

[[ Contents Previous Page | Next Page Index ]]