PI47698: DFHIS0002 A SEVERE ERROR(CODE X'030D') HAS OCCURRED IN MODULE DFHISIC.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CICS TS 5.2 system was under heavy CPU constraints at the time
  of the abend DFHIS0002.
  The CICS log also shows message:
  DFHIS1050 08/24/2015 10:17:24 IPCON1 HEARTBEAT RESPONSE TIMEOUT
            IN IPCONN IPCONN2.
  Analysis of the DFHIS0002 dump showed :
  CICS TS 5.2 is attempting autoinstall IPCONN ABCD but this fails
  when a duplicate IPCONN ABCD is detected by the CICS catalog
  domain. The IPCONN install is done by transaction CISS.
  Task 343 CISS fails with :
  00343 QR    GC 2050 CCCC  EXIT  ADD/EXCEPTION DUPLICATE
  00343 QR    IS 030D ISIC  *EXC* CC_ADD_FAILED
                                  AUTOINSTALL_IPCONN,CHSKARQ2,ABCD
  .
  We see that task 337 CIST has deleted IPCONN ABCD from TCTS BUT
  is currently suspended upon catalog delete of IPCONN ABCD:
  .
  00337 QR    GC 2010 CCCC  ENTRY DELETE   ISIPCONN,ABCD
  00337 QR    DS 0004 DSSR  ENTRY WAIT_MVS CCVSAMWT,NO,IO,EXCLOGER
  So IPCONN ABCD is not yet deleted from CICS Catalog.
  .
  Tasks 337 and 343 each appear to have an exclusive lock on ABCD.
  Looking at the full trace of each task ( LM entries - full shows
  lock names):
  task 337 has an exclusive lock on lock name ABCD but then
  task 343 does ADD_LOCK for ABCD and gets a new lock token ok.
  The CIST and CISS transactions appear not to be properly
  syncronised when deleting and re-adding the same IPCONN
  name.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHIS0002 A SEVERE ERROR(CODE X'030D')  *
  *                      HAS OCCURRED IN MODULE DFHISIC.         *
  *                      This message is issued while            *
  *                      attempting to autoinstall an IPCONN.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  CICS was running with restricted CPU and IPIC connections were
  timing out and being released due to heartbeat failures.
  This causes autoinstalled IPCONNs to be released and discarded.
  During the DISCARD the ISCB chain lock was used to synchronise
  removal of the IPCONN from the ISIN and ISIA directories
  but was released before removing the IPCONN from the CICS
  catalog. At this point the task was suspended.
  Meanwhile, a second task attempted to autoinstall an IPCONN
  with the same name. It added entries to the ISIN and ISIA
  directories and then failed on the attempt to add to the
  catalog because the DISCARD had not completed.
  This unexpected error was reported by a DFHIS0002 message
  with code X'030D'.
  Additional keywords: IS0002 MSGDFHIS0002
  

Problem conclusion

• CICS is changed so the routines dfhisic_discard_ipconn and
  add_iscb hold the ISCB chain lock while making the
  directory and the catalog updates.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UI32735

Modules/Macros

• DFHISIC
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R900 PSY UI32735

     UP15/11/12 P F511

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.