IBM Support

PH58857: KE_NUM TRACE FORMATTER DOES NOT ALWAYS SHOW THE EXPECTED TRACE ENTRIES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When formatting trace in a dump, like this:
    
    verbx dfhpd560 'trs=<ke_num=BC,full>'
    
    the "most recent trace entries" section sometimes does not show
    any trace entries for the requested ke_num even though there
    have been trace entries made for that kernel number.   When this
    problem happens, it looks like this:
    
    ===TR: MOST RECENT TRACE ENTRIES
    
    NO DATA AVAILABLE FOR SPECIFIED TASK
    
    There is a second problem that sometimes happens.  Sometimes
    the formatter shows trace entries for a ke_num that is different
    from the one requested.  For example, if trace for KE_NUM F7 is
    requested like this:
    
    verbx dfhpd740 'trs=<ke_num=f7,full>'
    
    Sometimes the output will show trace entries for a different
    KE_NUM, such as F9, like this:
    
    ===TR: MOST RECENT TRACE ENTRIES
    
    DATA FOR TASK WITH KE_NUM(00F9)
    
    00000 QR    DS 0008 RETADDR(9736A38E) TIME...
    00000 QR    DS 0009 RETADDR(9736A38E) TIME...
    . . . . . . .
    
    (The example output above is truncated on the right and on the
    bottom just to save space.)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: "most recent trace entries" section     *
    *                      in an IPCS formatted task trace not     *
    *                      displaying correct information.         *
    ****************************************************************
    The "most recent trace entries" section within a formatted trace
    from a dump such as:
    
    verbx dfhpd560 'trs=<ke_num=BC,full>'
    
    displays the 20 most recent trace entries. When a task has not
    had 20 trace entries in total, it can lead to this section
    sometimes not showing any trace entries for the requested ke_num
    even though there are trace entries that should be shown or the
    formatter may show trace entries for a ke_num that is different
    from the one requested.
    

Problem conclusion

  • CICS has been updated to handle the situation where the stalled
    task trace formatter is given a task with under 20 trace
    entries.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH58857

  • 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

    2023-12-19

  • Closed date

    2024-02-08

  • Last modified date

    2024-03-18

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

    PH57818

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

    UI95597

Modules/Macros

  • DFHTRDUF DFHTRPT  DFHTRPX  DFHTRSU
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R400 PSY UI95597

       UP24/02/09 P F402

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":"BU048","label":"IBM Software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
04 April 2024