IBM Support

Resp 88 Resp2 201 when running DB2 COBOL stored procedure to run EXCI transaction on different LPAR

Question & Answer


Question

Why am I receiving RESP=88 RESP2=201 when running a DB2 COBOL stored procedure to run an EXCI transaction on a separate LPAR? When DB2 and the CICS region are on the same LPAR, this works great. I now have a need to move the CICS region to another LPAR. Now when the EXCI transaction runs we get the following response codes are from DSNWIMST :

 S3105105 - ++ RETURN FROM EXCI:                         
 EXEC-RESP:    00000088                                  
 EXEC-RESP2:   00000201                                  
 EXEC-ABCODE:                                            
 EXEC-MSG-LEN: 00000000                                  
 EXEC-MSG-PTR: 0000000000                                

Answer

The following can be found in the CICS Transaction Server for z/OS (CICS TS) documentation in section Using EXEC CICS LINK command:

Error codes
Most of the exception conditions that are returned on the external CICS interface LINK command are the same as for the CICS-to-CICS distributed program link command. Those that are the same, and their corresponding numeric values are as follows:
. . .

LINKERR (RESP value 88)
This is returned when the EXCI module handling the EXEC CICS LINK request receives a RETRYABLE, USER_ERROR, or SYSTEM_ERROR response to an EXCI call issued on behalf of the EXEC CICS LINK command. The DPL request has failed. The RESP2 field is set to the EXCI reason code, which gives more information about the error.

If you review the Reason codes for response: RETRYABLE section under Response and reason codes returned on EXCI calls, you will see that Resp2 value 201 is documented as follows:

201: NO_CICS_IRC_STARTED

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.

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"EXCI","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSAU5Z","label":"COBOL Compilers"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server

Document Information

Modified date:
20 July 2021

UID

dwa1397972