PK35028: DFHZC2422 IS PRODUCED DURING BINDSECURITY PROCESSING

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer just migrated from CICS TS 2.3 to CICS TS 3.1. They
  are making use of BINDSECURITY across an LU62 connection. All
  setup is correct. Definitions are exactly the same as those used
  when running CICS TS 2.3. The BINDSECURITY processing is failing
  with message DFHZC2422 followed by message DFHZC3496. Failure
  is associated with instance 21 out of DFHZEV1.
    The problem appears to be within DFHZEV1 (base level) at label
  ZTR01B0385. There are actually two problems with this code.
  First, the register usage of REG A is incorrect when we test
  bit TCSEBSY to determine if BINDSECURITY is set on. REG A has
  just previously been used to test bit TCTELUC within the Session
  TCTTE. REG A is still pointing to the TCTTE when we test bit
  TCSEBSY. REG A shoud be set up to point to the System Entry
  (TCTSE) prior to testing bit TCSEBSY.
    Secondly, if the register usage was correctly pointing to the
  TCTSE when testing TCSEBSY, the BNZ logic following the test is
  incorrect and causes an invalid branch to label ZEV1ERR2. This
  should be BZ logic as we expect the TCSEBSY bit to be on.
    This failure will only be seen against the Contention Looser
  Sessions. Contention Winner Sessions process BINDSECURITY ok.
  Contention Winner Sessions work due to TCTTE +X'122'(bit TCTEBCL
  , bound as contention loser, being turned off. Contention Loser
  Sessions fail due to TCTEBCL being turned on, thus causing the
  BNZ logic to force branch to label ZEV1ERR2.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHZC2422 Logic error 21 module name    *
  *                      DFHZEV1 is received when trying to      *
  *                      bind an LU62 session for a connection   *
  *                      defined with BINDSECURITY YES.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An LU62 connection is defined with BINDSECURITY YES. A bind
  is received from the LU62 partner for a session TCTTE and
  DFHZEV1 is called to handle BINDSECURITY processing.
  DFHZEV1 contains an initial check to ensure that BINDSECURITY
  is active for this connection.
  
  This should check a flag in the system TCTTE but the session
  TCTTE is being addressed instead. A logic error is raised if the
  session TCTTE flag TCTEBCL happens to be on as this occupies the
  same position as the TCSEBSY flag in the system TCTTE.
  The bind will fail and a ZC3496 dump is taken accompanied by
  message DFHZC3496.
  
  ADDITIONAL KEYWORDS :- MSGDFHZC2422 MSGDFHZC3496 TCSEIBSY
                         LU6.2 APPC LUTYPE62 LUTYPE6.2
  

Problem conclusion

• DFHZEV1 has been changed to correctly address the system TCTTE
  before confirming that the BINDSECURITY flag TCSEBSY is on.
  

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:

  UK22192

Modules/Macros

•    DFHZEV1
  

Fix information

• Fixed component name

  CICSTS 3.1 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R400 PSY UK22192

     UP07/02/17 P F702

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.