IBM Support

PH33424: TRACE POINTS AP 0968 AND AP 0969 DO NOT FORMAT CORRECTLY APTRY *EXC* - UNABLE_TO_FORMAT_TRACE_POINT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Looking at CICS trace in a dump, you notice the
    following trace entries that do not format
    correctly:
    
    AP 0968 APTRY *EXC* - Unable_to_format_trace_point
    and
    AP 0969 APTRY *EXC* - Unable_to_format_trace_point
    
    They should be formatted as:
    
    AP 0968 APRP ENTRY
    and
    AP 0969 APRP EXIT
    .
    These trace entries are associated with
    transaction routing.
    The formatting trace module DFHAPTRI- incorrectly
    includes trace points beginning in range 0960, in
    a section associated with transaction manager trace.
    This leads to the exception trace being put out.
    
    Additonal symptoms:  KIXREVHJM
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Unable to format trace points AP 0968   *
    *                      and AP 0969.                            *
    ****************************************************************
    A change made to DFHAPTRI resulted in the wrong trace formatting
    module being called for trace points AP 0968 and AP 0969.
    Also affected by the change are trace points AP 0960, 0961,
    0962, 096A and 096B.
    This change was made to be able to use two new trace points for
    JSON PIJT.
    

Problem conclusion

  • DFHAPTRI has been changed to call the correct format module for
    the AP 0960 to 096B trace points.
    Two new trace points have been created for the JSON PIJT Entry
    and Exit, 5000 and 5001.
    DFHAPTRI has also been changed to call the correct format module
    for these new trace points.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH33424

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / CST / Xsystem

  • Submitted date

    2021-01-15

  • Closed date

    2021-06-23

  • Last modified date

    2021-07-13

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

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

    UI76017 UI76018 UI76019

Modules/Macros

  • DFH62XM  DFHALXM  DFHAMP00 DFHAPAC  DFHAPATT DFHAPCR  DFHAPCR1
    DFHAPDN  DFHAPHN  DFHAPNT  DFHAPPG  DFHAPRC  DFHAPSI  DFHAPTRI
    DFHAPTRY DFHAPXM  DFHAPXME DFHBEPB  DFHBEPC  DFHBRFM  DFHCAPB
    DFHCAPC  DFHCIS4  DFHCR1U  DFHCR2U  DFHCRIU  DFHCRL   DFHCRLB
    DFHICXM  DFHIEP   DFHIEXM  DFHISCOP DFHISEMP DFHISLQP DFHISPHP
    DFHISPRP DFHISREU DFHISREX DFHISRRP DFHISRSP DFHISXM  DFHLEPT
    DFHLEPTI DFHLETRI DFHMRXM  DFHOTR   DFHPIDSH DFHPIDSQ DFHPIJT
    DFHPILSQ DFHPIRI  DFHPIRT  DFHPITP  DFHPITQ1 DFHPSJP  DFHRDTRI
    DFHRLVC  DFHRMXN3 DFHSHSY  DFHSJL   DFHSJNS  DFHTDXM  DFHTFXM
    DFHTSDQ  DFHW2A   DFHWSATH DFHWSATR DFHWSATX DFHXCSCR DFHXFRM
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R100 PSY UI76019

       UP21/06/24 P F106

  • R200 PSY UI76018

       UP21/06/24 P F106

  • R300 PSY UI76017

       UP21/06/24 P F106

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.

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

Document Information

Modified date:
14 July 2021