A fix is available
APAR status
Closed as program error.
Error description
CICS is connected to an IPIC partner on a TxSeries box. When the TxSeries box is terminated abruptly, CICS expects to be notified via TCPIP POSTing our SOCKET INBOUND active RECEIVE as complete with a socket closed (EIO). Because this never happens, the IPIC connection on the CICS HOST side does not and can not be cleaned up or cleared for reuse. . Attempts to RELease the IPCONN results in the IPCONN going into FREEING state forever. There is no facility within CICS to recover other than having to restart CICS.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: IPCONN unable to be released after * * partner system unexpectedly terminates. * **************************************************************** * RECOMMENDATION: * **************************************************************** CICS is connected to a partner system (in this case TXSeries) using IPIC. The other system unexpectedly terminates. When this happens CICS is not notified that the connection has been terminated and the IPCONN in CICS remains in INS ACQ state. A CEMT SET IPCONN RELEASED command is issued. This causes the IPCONN to get stuck in FREEING state. The CICS region has to be recycled to get the IPCONN working again. The IPCONN was stuck in FREEING state because CICS was waiting for the other system to close its outbound sockets. The IPCONN will not go to a RELEASED state until that happens. The other system is no longer available so cannot close these sockets. An additional problem with an IPCONN being stuck in FREEING state is when a CICS to CICS IPCONN is being used and the CICS system that initiates the acquiring of the IPCONN has less than 2 sockets available to it. When this happens the attempt to acquire the IPCONN will fail. Everything is backed out on the initiating system and the IPCONN set back to INS REL state. The IPCONN on the partner CICS system will be left in INS FRE state and CISS will be waiting for resync data to arrive. The wait occurs even though CICS has already been notified that the connection has closed.
Problem conclusion
The CICS IPIC code has been changed to no longer wait for the partner system to close its sockets when setting the IPCONN to RELEASED. The CISS task will no longer continue to wait for resync data when the attempt to acquire the IPCONN has failed and the socket is now closed.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM62347
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
500
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-04-12
Closed date
2012-06-29
Last modified date
2012-08-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK79948
Modules/Macros
DESISCO DESISEM DESISRE DESISRR DFHISCO DFHISEM DFHISRE DFHISRR
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R500 PSY UK79948
UP12/07/11 P F207
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
08 August 2012