Question & Answer
Question
How is the CICS Transaction Gateway (CICS TG) IPIC Sessions limit is determined? I have defined the IPIC connection (IPCONN) in my test CICS Transaction Server for z/OS (CICS) with a RECEIVECOUNT of 250. However, when the IPIC Connection acquires with CICS TG, message CTG8429I indicates the session count is 75:
CTG8429 I Established new IPIC connection to CICS server (servername) with: negotiated session limit=75,
CICSAPPLID=(applid) CICSAPPLIDQUALIFIER=(qualifier) , HOSTNAME=localhost, PORT=(portnumber), sockets=2
In our production environment, IPIC Connections have a RECEIVECOUNT of 100 and the negotiated session limit is 100:
CTG8429I Established new IPIC connection to CICS server (servername) with: negotiated session limit=100,
CICSAPPLID=(applid) CICSAPPLIDQUALIFIER=(qualifier) , HOSTNAME=(hostname), PORT=(portnumber), sockets=2
I don't understand what would cause the port not to accept more than 75 IPIC Sessions.
Answer
Table 1. How the number of simultaneous transactions possible over an IPIC connection is determined, within topic Configuring IPIC on CICS Transaction Server for z/OS of the CICS Transaction Gateway for Multiplatforms documenation, depicts how Session limits are set.
With the information provided in the above question, the only possibility is explained by the first row of the table. It explains the SENDSESSIONS setting in CICS Transaction Gateway must be set to a lower value than the IPCONN Receive Count setting in CICS Transaction Server. In this case, the lesser of the two values is used.
In this case, it was discovered that the SENDSESSIONS setting in CICS TG was set to 75 for the new Connection so it was overriding the IPCONN RECEIVECOUNT value of 250 in CICS TS.
Product Synonym
CICSTG CICS TG;CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
05 December 2018
UID
dwa1482576