IBM Support

PH48880: ABEND0C4 IN DFHTRPX + X'38E' AND DFHTR0112 BAD DATA PASSED FOR TRACING TO MODULE DFHTRPT.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An abend0c4 PIC11 occurred in DFHTRPX at offset x'38E' on an ICM
    instruction.
                                                                   .
    This was during processing for a trace data object.
    The object was a console name, 4 bytes in length. The
    abend0c4 occurred due to trying to reference further than this,
    past the end of the trace data, where storage was not currently
    allocated.  In this case into a
    new 4k page.
    Message DFHTR0112 ... Bad data passed for tracing to module
                          DFHTRPT
                                                                   .
    Trace entry flow:
    QR    AP FCA3 ZATA2 ENTRY INSTALL_CONSOLE
    QR    AP FCA3 ZATA2 ENTRY SIGNOFF_SIGNON
    QR    TR 0102 TRPT  *EXC* INVALID-DATA-PASSED   : CALLING DOMAIN
                 WAS AP : PARAMETER LIST WAS TRACE_PUT,FCA3,194F8FEC
    QR    ME 0301 MEME  ENTRY SEND_MESSAGE
                 70,TR0112,1085CBC8 , 00000007,TR
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: An intermittent abend0c4 can occur in   *
    *                      tracing modules DFHTRPX and DFHTRPT.    *
    ****************************************************************
    Following the code changes during development of CICS 5.6 to
    provide the capability to format recent trace entries for tasks
    there is logic in both the fastpath (DFHTRPX) and normal
    (DFHTRPT) trace routines to store a potential function code.
    This value is:
    - obtained from offset 24 in the first variable piece of data
    traced
    - stored into the Task trace entry, which is a new structure
    at the 5.6 release.
    
    When the following conditions apply, a program check can occur:
    - the first variable piece of traced data is less than 28 bytes
    in length
    - the variable piece of traced data is at the end of a page
    - the following page is either not owned or is in a different
    protect key.
    

Problem conclusion

  • Modules DFHTRPT and DFHTRPX were modified so that the lookup
    and store of the potential function code is no longer done
    when the first variable piece of traced data is less than 28
    bytes in length.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH48880

  • Reported component name

    CICS TS Z/OS V6

  • Reported component ID

    5655YA100

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-08-24

  • Closed date

    2022-10-11

  • Last modified date

    2022-11-01

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

    PH45419

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

    UI82786

Modules/Macros

  • DFHTRPT  DFHTRPX
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R400 PSY UI82786

       UP22/10/25 P F210

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
01 November 2022