PK71189: DFHTR0112 BAD DATA PASSED FOR TRACING TO MODULE DFHTRPT FOR A PROGRAM USING THE JCICS API

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Abend0C4 's occur in DFHTRPX and DFHTRPT, followed by message:
  .
  DFHTR0112  BAD DATA PASSED FOR TRACING TO MODULE DFHTRPT.
  .
  The problem occurs when trying to put out trace entry:
  .
  AP 21E0 JCICS EXIT Container_PUT
  .
  Trace shows that there was a JCICS call. A wrapper layer makes a
  trace entry and then makes it look like an EXEC CICS
  PUT-CONTAINER. On return, it is trying to write an exit trace
  entry and return back to the Java program. It looks like the
  wrapper code making the trace call with an invalid parameter is
  Container.c.  The problem appears to be on it's last parm,
  variable cContainer which is x'10' bytes long.
  .
  The problem is that the storage for cContainer has been freed by
  the time it gets traced out on the exit trace. The storage is
  just released back to the LE heap so most of the time it is
  still addressable but contains garbage.  This doesn't cause an
  0C4. In this case LE would have freed the whole page and given
  it back to z/OS. So for this case, the storage is no longer
  accessible and that causes the 0C4 and resulting DFHTR0112
  message.
  .
  Additional Symptom(s) Search Keyword(s): KIXREVWJB S0C4
  ABENDS0C4
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHTR0112 Bad data passed for tracing   *
  *                      to DFHTRPT.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A Java application is using the JCICS container classes to
  handle the containers. The put() method is called
  which results in an EXEC CICS PUT CONTAINER command being
  issued. The command works successfully, but on return routine
  Java_com_ibm_cics_server_Container_PUT attempts to write an
  exit trace entry and uses an invalid address for the container
  name.
  This may lead to invalid output or an ABEND0C4.
  
  Additional Keywords: ABENDS0C4 S0C4 0C4 MSGDFHTR0112
  

Problem conclusion

• Program container.c has been changed to pass the correct
  container name on all exit trace entries.
  

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:

  UK41153 UK41154

Modules/Macros

•    DFJDTCOE
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R40D PSY UK41153

     UP08/10/31 P F810

• R50D PSY UK41154

     UP08/10/31 P F810

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.