PH31764: DFHAP0002 A SEVERE ERROR (CODE X'4C4C') HAS OCCURRED IN MODULE DFHBRME

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When running under the link3270 Bridge, a severe error can
  occur in DFHBRME when a user transaction issues an EXEC CICS
  RECEIVE that requires the driver to return to the client
  application for more data.
  
  The user transaction should trigger the driver partner (CSMI)
  and suspend to wait for the partner to return the data. Control
  then passes to the driver which breaks the partnership between
  the two tasks and reinstates it when the data is available.
  
  In the failing case the user transaction loses control between
  triggering the driver and issuing its suspend. CSMI breaks the
  partnership and suspends on an IRLINK when contacting the
  router region. The user transaction runs to the suspend but the
  code expects the partnership to still exist so DFHPTTW
  WAIT_FOR_PARTNER returns PARTNER_NOT_THERE and a severe error
  is reported
  
  In the trace you see a corresponding entry like the following:
  
  AP 4C4C BRME  *EXC* - PTTW_UNEXPECTED_ERROR -
  FUNCTION(API_EMULATOR) BRXA(XXXXXXXX)
  
  Additional Symptom(s) Search Keyword(s): KIXREVxxx
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHAP0002 severe error code X'4C4C'     *
  *                      has occurred in DFHBRME.                *
  ****************************************************************
  Customer receives DFHAP0002 Severe error x'4C4C in DFHBRME when
  a client program is using the LINK3270 Bridge. The user
  transaction has established a partnership. The user transaction
  has issued a request for more data from the client and has then
  issued a TRIGGER_PARTNER call. Its partner then does a
  BREAK_PARTNERSHIP call that completes before the user
  transaction issues a WAIT_FOR_PARTNER call with the
  partner_existence parameter set to MUST_EXIST.
  This call gets an EXCEPTION, PARTNER_MUST_EXIST
  severe error. This led to the DFHAP0002 dump.
  
  Additional keywords: MSGDFHAP0002
  

Problem conclusion

• DFHBRME has been changed to no longer require the partner to
  exist when it makes the WAIT_FOR_PARTNER call.
  

Temporary fix

Comments

APAR Information

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

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

  UI74528 UI74529

Modules/Macros

• DFHBRME
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R200 PSY UI74529

     UP21/03/23 P F103

• R300 PSY UI74528

     UP21/03/24 P F103

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.