IBM Support

PH65597: ADDITIONAL FC LEVEL 2 TRACE DATA

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Additional FC level 2 trace data
    DFHFCFR does not trace out the FCT on exit from an API
    operation. This is different to DFHFCFS (file state
    changes) and DFHFCMT (file table management) which both
    trace the associated FCT on exit.
    Having DFHFCFR do this also (for FC level2 tracing) would
    greatly assist problem determination for problems involving
    CICS files, with limited trace data (or the need for
    closer monitoring of FCT flags fields).
    Note - DFHFCVS can also be considered for this enhancement,
    for local VSAM files. And perhaps DFHFCRS for RLS files.
    Note also - we can easily trace FCTs on exit from a module,
    whereas on entry to the module the FCT pointer is unlikely
    to be set up at such an early point in the proceedings.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: DFHFCFR has no file control level 2     *
    *                      trace option to print the FCT as part   *
    *                      of its exit level 2 trace call.         *
    ****************************************************************
    CICS file control API commands will drive DFHFCFR on entry and
    exit to the file control component. It would assist CICS
    serviceability for DFHFCFR to trace the FCT on exit if desired.
    

Problem conclusion

  • CICS has been changed to issue new trace point AP 04ED on exit
    from DFHFCFR if the file control standard level 2 trace setting
    is specified. This will trace the content of the FCT at that
    time, if one exists and the request is not for a remote file.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH65597

  • Reported component name

    CICS TS Z/OS V6

  • Reported component ID

    5655YA100

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-03-11

  • Closed date

    2025-04-01

  • Last modified date

    2025-05-02

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

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

    PH65847 PH65848 UO02659

Modules/Macros

  • DFHAPTR5 DFHAPTRE DFHAPTRI DFHDT64M DFHDTINS DFHDTLA  DFHDTLI
    DFHDTLX  DFHDTRC  DFHDTRE  DFHDTRI  DFHDTRR  DFHDTSS  DFHDTST
    DFHDTUP  DFHEIFC  DFHEIQCF DFHEIUOW DFHFCAT  DFHFCBU  DFHFCCA
    DFHFCDL  DFHFCDN  DFHFCDO  DFHFCDR  DFHFCDTS DFHFCDTX DFHFCDU
    DFHFCDW  DFHFCDY  DFHFCES  DFHFCFL  DFHFCFR  DFHFCFS  DFHFCIR
    DFHFCL   DFHFCLF  DFHFCLJ  DFHFCM   DFHFCMT  DFHFCN   DFHFCNQ
    DFHFCOR  DFHFCQI  DFHFCQR  DFHFCQS  DFHFCQT  DFHFCQU  DFHFCQX
    DFHFCRC  DFHFCRD  DFHFCRF  DFHFCRL  DFHFCRN  DFHFCRO  DFHFCRP
    DFHFCRR  DFHFCRS  DFHFCRV  DFHFCSD  DFHFCST  DFHFCVC  DFHFCVR
    DFHFCVS
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R500 PSY UO02659

       UP25/04/03 P F504

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.2","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
02 May 2025