OA36087: IXLCONN FAILS RC0C RSN02010C09 LOCK OR SERIALIZED LIST STR

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A IXLCONN to a lock or serialized list structure will fail with
  IXL013I indicating RC0C RSN02010C09 and the following CONADIAG
  values:
  CONADIAG0:   00000002 = ASRDiagForCona
  CONADIAG1:   00000008 = ASRRetCode
  CONADIAG2:   00010C09 = ASRRsnCode = ASRARsnCodeNoConnections
  CONADIAG10:  00400000 = Bit = Ap_Stbl_ClearLt_Inprogress
  
  New connections to the structure are prevented when a Clear lock
  table function is in progress. There is a bit in the active CFRM
  policy indicating the lock table associated with the serialized
  list or lock str is being cleared.  This process is kicked off
  when the last connection disconnects or or on a complete/stop of
  system managed process. An XCF signal is sent from the system
  where the last connector to the str is running to all others and
  then there is a race for one of the systems to own the process
  by updating its sysid in the active policy on the CFRM CDS in
  Ap_Stbl_ClearLT_Owningsys.
  
  If the system performing the clearlt process is partitioned
  before complete and the system which takes over does not have
  connectivity to the CF or is going through partitioning, all
  Connects to the structure will fail and the connector may hang
  redriving the IXLCONN like we found JES2 did.
  
  
  
   VERIFICATION STEPS:
   1. IXL013I for IXLCONN failure with RC=0C RSN=02010C09
      CONADIAG0:   00000002
      CONADIAG1:   00000008
      CONADIAG2:   00010C09
      CONADIAG10:  00400000
   2. D XCF,STR,STRNAME=  response in msg IXC360I shows:
      STRUCTURE CLEANUP IN PROGRESS
      and small # of lock entries in use:
      LOCKS: 2
   3. An ADRDSSU print of the CFRM CDS active policy shows:
      Ap_Stbl_ClearLt_Inprogress=on  and the system identified
      in Ap_Stbl_ClearLT_Owningsys was partitioned while it was
   performing the clearlt process and the takeover system
   either did not have connectivity to the CF in that timeframe
   or was partitioned as well.
   4. Verify in operlog that the system identified above was
   partitioned and other systems were also partitioned or loss
   connectivity in a very close timeframe
  

Local fix

• BYPASS/CIRCUMVENTION:
   To clear the condition and bring the structure back into use do
   a SETXCF FORCE,STR,STRNAME= command and then redrive the
   application to reconnect to the structure.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of z/OS V1R10 (HBB7750) and above in   *
  *                 a Parallel Sysplex environment.              *
  *                                                              *
  *                 SYSPLEXDS                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: A CF (coupling facilitiy) structure may *
  *                      enter the STRUCTURE CLEANUP IN PROGRESS *
  *                      state when the structure type is        *
  *                      serialized list or lock and all active  *
  *                      CF structure connections terminate.     *
  *                      Partitioning a system                   *
  *                      from the sysplex while a structure is   *
  *                      in that state may cause the system to   *
  *                      lose initiative to complete the cleanup *
  *                      processing. Until the cleanup           *
  *                      processing completes, or the structure  *
  *                      is forced, the structure will remain    *
  *                      in that state and will not be usable.   *
  ****************************************************************
  * RECOMMENDATION: Fix should be installed via rolling IPL.     *
  *                 This fix will not be fully effective on the  *
  *                 system it is being applied until this fix is *
  *                 applied to all systems in the sysplex. Until *
  *                 all systems in the sysplex have this fix, a  *
  *                 system without the fix may not provide the   *
  *                 proper initiative to complete the CF         *
  *                 structure cleanup processing. An IPL is      *
  *                 required to activate this fix on each        *
  *                 system, however, a rolling IPL is sufficient *
  *                 to accomplish the activation.                *
  ****************************************************************
  When a system is partitioned from the sysplex, one surviving
  system may take responsibility for taking over CF structure
  cleanup processing. If the system is unable to perform the
  cleanup processing (due to being removed from the sysplex or
  no connectivity to the CF), initiative to perform the
  cleanup processing is lost.
  

Problem conclusion

• Corrected system termination processing in module IXCL2RSR that
  queued a local request to take over cleanup processing to
  instead unassign cleanup processing and signal all systems to
  attempt to take over cleanup processing. The corrected logic
  will maintain initiative to perform CF structure cleanup
  processing.
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  UA60829 UA60830 UA60831 UA60832

Modules/Macros

• IXCL2RSR
  

Fix information

• Fixed component name

  XCF

• Fixed component ID

  5752SCXCF

Applicable component levels

• R750 PSY UA60829

     UP11/06/22 P F106 Ž

• R760 PSY UA60830

     UP11/06/22 P F106 Ž

• R770 PSY UA60831

     UP11/06/22 P F106 Ž

• R780 PSY UA60832

     UP11/06/22 P F106 Ž

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.