PM50853: DFHME0121 WHEN MESSAGE DFHIS6002 OR DFHIS6003 IS ISSUED IF XID CONTAINS BAD CHARACTERS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DFHISRE (UK67848) is issuing DFHIS6003 or DFHIS6002 because a
  communication error has occurred after the UOW has been
  committed (isre_msg_comms_failed_uow_committed). The message
  has an insert for the XID. PM21789 introduced code in
  dfhisre_format_xid_insert to convert the XID from Hex to
  Printable chars. This code uses variable xid_gtrid_length to
  control the number of bytes converted.  This variable is taken
  from the Recovery List item for this resync request.
  
  So the length contains spaces (4040) which results in a huge
  overlay and subsequently a bad character in this area resulting
  in the DBCS error.
  
  There is a problem with procedure DFHISRE_FORMAT_XID_INSERT.
  

Local fix

• No Local Fix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: msgDFHME0121 is issued when attempting  *
  *                      to format message DFHIS6003.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A CICS TG client is connected to CICS via IPIC.  Due to an
  earlier failure there are indoubt units of work that need to be
  resolved.  CICS TG sends an XA resync message to CICS supplying
  the XID of the unit of work that requires resync.
  
  The CICS unit of work is located and resync is successful.  A
  response message is built but the attempt to send this message
  back to the CICS TG client fails.  This failure causes DFHISRE
  to issue message DFHIS6003.
  
  Message DFHIS6003 contains the supplied XID and the located
  UOWID as inserts.  The XID is a hex value so must be converted
  into a printable format for the message.  The formatting routine
  expects the current IS field to be the IS12 containing the XID.
  This is not the case and causes incorrect storage to be used as
  the XID for the message insert.  The length of the XID is also
  incorrect and in this case was x'4040' leading to x'8080' bytes
  of converted output.  The unexpectedly large amount of output
  causes an overlay of the end of the stack for DFHISRE and
  subsequent stack storage areas.
  
  When message domain builds the message DFHMEFO detects invalid
  DBCS data within the x'8080' bytes and issues message DFHME0121.
  
  The same problem may also occur for messages DFHIS6002 and
  DFHIS6004.
  
  Additionally the UOWID insert for messages DFHIS6003 and
  DFHIS6004 is incorrect.
  
  Additional keywords:
  ME0121  IS6002  IS6003  IS6004  msgDFHIS6002  msgDFHIS6003
  msgDFHIS6004
  

Problem conclusion

• DFHISRE has been changed so that the XID is correctly formatted
  as part of messages DFHIS6002, 6003, 6004 and 6005.  The UOWID
  insert for messages DFHIS6003 and DFHIS6004 has also been
  corrected.
  

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:

  UK75923 UK75924

Modules/Macros

•    DESISRE  DFHISRE
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R600 PSY UK75923

     UP12/02/10 P F202

• R700 PSY UK75924

     UP12/02/10 P F202

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.