IBM Support

CICS ISC connection does not AUTOCONNECT after network becomes available

Question & Answer


Question

Can you tell me why an ISC connection between two CICS regions does not AUTOCONNECT after the network becomes available? I lost an ISC connection between CICS regions due to a network change. I thought the session would autoconnect after the network became available since I have AUTOCONNECT=YES specified in the CONNECTION definition.

Answer

For the intersystem communication (ISC) connection, when you specify "Yes" for the AUTOCONNECT attribute of a CONNECTION resource this does not mean CICS will keep trying to connect. If the other side is available, CICS will try to connect. But if the remote system is not available, CICS will not keep trying to connect because CICS could end up in a loop trying to connect over and over again.

If your network becomes unavailable in the future, you can enter the following command in CICS then CICS will try to connect to the remote system:

CEMT SET CONNECTION(value) INSERVICE ACQUIRED

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

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server

Document Information

Modified date:
10 April 2017

UID

dwa1365555