Question & Answer
Question
Your batch jobs fail with maxcc 8 when attempting an EXCI distributed program link (DPL) request with RESP 8 , RESP2 202.
The Batch Joblog shows the following error:
EXCI CALL FAILED - CALL TYPE WAS OPEN PIPE CICSxx
GNBX001 ** EXCI CALL PROCESS FAILED - LINK RESP CODES FOLLOW:
GNBX001 RESP: 00000008 RESP2: 00000202 SUB REASON1: 00000000
Section 202: NO_PIPE of the CICS documentation seems to indicate there are not enough available sessions to perform the request. LOGONLIM is set to the default value of 100 pipes. The EXCI SESSIONS RDO definition is configured to have a RECEIVECOUNT of 10.
Answer
Section 202: NO_PIPE of the CICS documentation does say the response code 202 NO_PIPE indicates that there are not enough receive sessions on the CICS side to handle the request. Most likely the defined 10 sessions are busy satisfying other request at that time. Increasing the number of receive sessions should resolve.
Keep in mind that LOGONLIM, in respect to EXCI, is the number of pipes allowed for an EXCI address space (the batch address space in this instance). So if the batch job is making request to more than one CICS region, you need to take that into consideration. Meaning, if LOGONLIM is 100, for the batch address space, and the batch address space is talking to 5 CICS regions, then you would not want to code more than 20 receive sessions on each of the 5 CICS regions. This is to ensure none of the CICS regions are able to get more than the others and possibly starve the other regions of EXCI pipes. If 100 is not enough, then increase the number (LOGONLIM) and allocate them evenly to the CICS regions.
Formula:
LOGONLIM / Number of CICS regions EXCI address space is connected to = Number of receive sessions allowed for each CICS region
(where "/" means divided by)
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
24 March 2020
UID
dwa1510101