PK96944: DFHAP0002 - SEVERE ERROR (CODE X'4C4C') IN DFHBRME FOR BRIDGE FACILITY APPLICATION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You receive DFHAP0002 - A severe error (code X'4C4C') has
  occurred in DFHBRME.  The failing task is a conversational
  bridge task.  However, before the bridge task could perform
  its SEND/RECEIVE, the driver task got terminated through a
  PURGE or TIMEOUT.  At this point, the state of the driver task
  ( PTTWSB_TRIGSTATE ) will be PTTWSB_TRIGSTATE_VALID and the
  state of the overall partnership ( PTTWSB_STATE ) will be
  PTTWSB_STATE_MADE.
  If the driver task had been resumed by the bridge task (which is
  what you would normally expect) and the bridge task is
  conversational, then the driver task would break its side of the
  conversation at this point and PTTWSB_STATE would become
  PTTWSB_STATE_PARTIALLY_MADE. However, this doesn't happen and
  the driver task terminates.  So at this stage, the state
  information doesn't reflect the real state of the
  DRIVER <-> BRIDGE.
  Eventually the bridge task gets running and issues its
  SEND/RECIEVE.  DFHPTTW is called for TRIGGER_PARTNER.  The
  state of the partnership is MADE and the state of the driver is
  VALID.  So it appears to DFHPTTW that the driver task is in the
  correct state to be triggered but it hasn't actually issued its
  WAIT_FOR_PARTNER yet.  The state of the driver is set to
  TRIGGERED - the expectation being that when the driver issues
  its WAIT_FOR_PARTNER it will get resumed immediately.
  Of course the driver task has already terminated. The bridge
  task now waits to be triggered by the driver.  This never
  happens.  Eventually the bridge task times out (or is purged)
  and starts to abend.
  The trace will show exception entries similar to:
  PT 0105 PTTW *EXC* PURGED - FUNCTION(RESUME) RESPONSE(EXCEPTION)
  REASON(TIMED_OUT)
  AP 4C4C BRME  *EXC* - PTTW_UNEXPECTED_ERROR -
  FUNCTION(API_EMULATOR) BRXA(4227B0B8)
  .
  Additional Symptom(s) Search Keyword(s):
  KIXREVGJT
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHAP0002 severe error code X'4C4C'     *
  *                      has occurred in DFHBRME.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Customer receives DFHAP0002 Severe error x'4c4c' in DFHBRME
  when a bridge task (attached via link bridge) terminates with
  an abend. DFHBRME_ABEND_ROUTINE has issued a DFHPTTWM
  TRIGGER_PARTNER call and this has returned an EXCEPTION with
  reason PTTW_ALREADY_TRIGGERED, causing the AP0002 dump.
  The bridge task is conversational and the bridge client
  transaction has been purged before the bridge transaction
  issued a call to DFHPTTWM TRIGGER_PARTNER as part of its
  RECEIVE processing. The purge of the client did not cause the
  state of the partnership to be altered to reflect the fact
  that the client was no longer there. So the TRIGGER_PARTNER
  issued by the bridge transaction went into a wait, expecting
  to be resumed by the client. Eventually the bridge task was
  purged or timed-out and, during abend processing, issued
  another TRIGGER_PARTNER. This time a logic error was detected
  by DFHPTTW as the state of the partnership was already set to
  TRIGGERED. This led to the DFHAP0002 dump.
  Additional keywords: MSGDFHAP0002
  

Problem conclusion

• DFHBRLK has been altered to issue a DFHPTTWM
  BREAK_PARTNERSHIP call if the bridge client is purged
  during it's WAIT_FOR_PARTNER call to the bridge. This will
  ensure that the state of the partnership is updated to reflect
  the fact that the bridge client no longer exists.
  DFHBRME has also been altered to abend with a new code ABRP
  if the bridge transaction has issued a DFHPTTWM
  TRIGGER_PARTNER call with PARTNER(MUST_EXIST) and the client
  no longer exists.
  .
  The CICS Transaction Server for z/OS Messages and Codes,
  GC34-6827-02, Chapter 3. Transaction abend codes, will have a
  new abend code ABRP added:
  .
  ABRP
  .
  Explanation:  The bridge client is no longer available.
  .
  System action:  The task is abnormally terminated
  with a CICS transaction dump.
  .
  User response:  Determine why the bridge client is no
  longer available. It might have been purged.
  .
  Module:  DFHBRME
  

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:

  PM02678 UK52937

Modules/Macros

•    CHAPT021 DESBRLK  DESBRME  DESBRTRI DFHBRLK
  DFHBRME  DFHBRMEA DFHBRMEC DFHBRMEM DFHBRMET DFHBRTRI DFHBRTR2
  DFH96944
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R500 PSY UK52937

     UP09/12/21 P F912

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.