PM97164: DFHAP0002 SEVERE ERROR (CODE X'4A45') OCCURRED IN MODULE DFHBRMG ISSUE ABENDABRP

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You are experiencing DFHAP0002 severe error (code X'4A45')
  occurred in module DFHBRMG issue.
  .
  The trace shows the following,
   AP 4A40 BRMG  ENTRY ALLOCATE_VECTOR
                 MESSAGE_TOKEN(00FDAD48)
                 VECTOR_TYPE(HEADER) TERMINATE(YES)
   AP 4A45 BRMG  *EXC* INVALID_MESSAGE_TOKEN
                 FUNCTION(ALLOCATE_VECTOR)
                 MESSAGE_TOKEN(00FDAD48) VECTOR_TYPE(HEADER)
                 TERMINATE(YES)
  .
  DFHAP0002 code X'4A45' in DFHBRMG is because
  BRXA_USER_AREA_PTR is zero, it is zero because we have
  ended up driving DFHBRXM RELEASE_XM_CLIENT twice.
  .
  The first time through is the normal task termination call.
  This finds that the partner is no longer there so sets
  a deferred abend of ABRP. DFHBRME then tidies up the bridge
  state which includes setting the BRXA_USER_AREA_PTR to 0.
  .
  The task gets abended ABRP and then DFHBRXM gets driven again
  in the abend path.
  .
  DFHBRXM and the DFHBRME code it invokes are not expecting to
  be driven twice so do not have checks for control blocks
  that "should" always exist at that stage.
  .
  We need ensure that DFHBRXM only gets called once for
  RELEASE_XM_CLIENT during task termination.
  .
  Additional Symptom(s) Search Keyword(s): KIXREVrer TIMED_OUT
  abendAEXY PARTNER_NOT_THERE abendABRP DFHAP0002 AP0002
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHAP0002 severe error code X'4A45' has *
  *                      occurred in DFHBRMG.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The bridge client has been purged after the bridge task(attached
  via link bridge) has started but before it starts going through
  task termination.
  When the bridge task starts going through task termination,
  DFHBRXM RELEASE_XM_CLIENT gets called for a NORMAL termination.
  It finds that the partner is no longer there so sets a deferred
  abend of ABRP. DFHBRME then tidies up the bridge state which
  includes setting the BRXA_USER_AREA_PTR to 0. The task gets
  abended ABRP.
  Then DFHBRXM RELEASE_XM_CLIENT gets called again for a NORMAL
  termination. DFHBRME calls DFHBRMG ALLOCATE_VECTOR to update the
  message vectors. When DFHBRMG tries to use BRXA_USER_AREA_PTR
  which is now 0, customer receives DFHAP0002 severe error code
  X'4A45' in DFHBRMG.
  
  Additional keywords: msgDFHAP0002 abendABRP
  

Problem conclusion

• DFHBRXM has been changed to not tidy up the bridge state when
  DFHBRXM RELEASE_XM_CLIENT is called for the first time as a
  NORMAL termination but then switches to ABNORMAL due to a
  deferred abend.
  
  When DFHBRXM abended during RELEASE_XM_CLIENT processing,
  DFHXMAT has been changed to ensure DFHBRXM RELEASE_XM_CLIENT
  is invoked for a second time for ABNORMAL termination and then
  tidy up the bridge state.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PM95028

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

  UI11648

Modules/Macros

• DFHBRXM  DFHXMTA
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R800 PSY UI11648

     UP13/11/01 P F310

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.