IBM Support

PH03960: TRACE ENTRY INDEX NUMBER IS 6 DIGITS - THIS NUMBER WRAPS IN LARGE TRACES DATASETS AND CONFUSES SOME FORMATTING TOOLS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • RTC item 102308.  A large trace can easily have over a million
    entries.  The index to reference the entries is only 6 digits
    so when it goes over 999999, the next entry is identified as
    000000 ( it wraps ).  Not only is this confusing, it breaks
    some formatting tools.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Trace entry sequence numbers are capped *
    *                      at 6 digits.                            *
    ****************************************************************
    This problem presents when processing a CICS trace that contains
    more than 999999 entries.
    
    The next trace entry sequence (entry_num) after 999999 will be
    000001 and subsequent trace entries will increment until
    999999 is reached.  This behaviour will repeat until all the
    trace entries in the trace table are processed. When this
    occurs, the output presented to the user will have instances of
    trace entry numbers (by entry_num) containing different
    trace entries.  Dump formatting tools which select trace entries
    by an entry_num range will only select the first instance.
    

Problem conclusion

  • Dump formatting code has been amended to increase the entry_num
    range of a CICS trace from 999999 to 9999999.
    
    The Knowledge Center will be amended.  The KC references IBM
    supplied tool DFHTUxxx, DFHPDxxx and DFHDUxxx which are
    all capable of formatting CICS trace entries.  The detailed
    syntax only appears against DFHTUxxx (with DFHPDxxx and DFHDUxxx
    referring to DFHTUxxx).
    The description of the trace entry index ( entry_num ) contain
    6 character representations of entry_num thus:
    nnnnnn, 999999, and xxxxxx-yyyyyy.
    These will be amended to:
    nnnnnnn, 9999999 and xxxxxxx-yyyyyyy respectively
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH03960

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-11

  • Closed date

    2019-01-30

  • Last modified date

    2019-03-01

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

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

    UI61022 UI61023 UI61024 UI61025 UI61026

Modules/Macros

  • DFHTRDUF DFHTRFFE DFHTRFPP DFHTRPRA
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI61026

       UP19/02/02 P F902

  • R100 PSY UI61025

       UP19/02/02 P F902

  • R200 PSY UI61022

       UP19/02/09 P F902

  • R800 PSY UI61024

       UP19/02/05 P F902

  • R900 PSY UI61023

       UP19/02/02 P F902

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 March 2019