IBM Support

PK30083: A LOOP MAY OCCUR IN DFHPD640 WHEN FORMATTING A SVC DUMP. THESE SYMPTOMS MAY OCCURR FORMATING THE DISPATCHER OR EXCLUDING LINES

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Reference returned APAR PK26292.
    Intermittently the CICS dump formatter will loop when the
    dispatcher control blocks have been formatted out in either
    summary form or detail, i.e. 'DS', 'DS=1', or 'DS=3'. The loop
    can occur when excluding lines within the dispatcher report,
    searching within the report, or other activity while viewing
    the report. If a dump is taken of the TSO userid's address
    space, the MVS System trace will show repeated SVC 78s(getmains&
    feemains)from the DFHDUFUT routine within the DFHPD640 module.
    DFHDSDUF is calling DFHDUFUT during the output formatting,
    and it appears that a GETSTORE request is failing.
    The return code is not being propagated back to DSDUF,
    and the operation is retried.
    DFHDSDUF is attempting to access the TCBs in the address space.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: IPCS may loop when formatting           *
    *                      Dispatcher statistics.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In the reported problem IPCS was looping when formatting
    Dispatcher statistics.
    
    DFHDSDUF contains code that will format out the statistics for
    each TCB. As part of this processing, it does a DFHDUFM call to
    GET_BLOCK a piece of storage from the dump. However, there is no
    error handling after this call. The call used a bad address in
    SCAN_PTR and the call failed. Rather than exit with an error (as
    happens elsewhere in dump formatting code whenever a bad address
    is encountered), the code looped, retrying the same request.
    
    Keywords: MSGDFHPD0103 DFHPD0103
    

Problem conclusion

  • DFHDSDUF has been modified and will now handle the
    aforementioned error situation by exiting the code that is
    formatting the Dispatcher statistics with an error of:
    
    DFHPD0103  DS_TCB address <actual_address> is invalid.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK30083

  • Reported component name

    CICSTS 3.1 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / CST

  • Submitted date

    2006-08-17

  • Closed date

    2006-09-14

  • Last modified date

    2006-10-11

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

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

    PK30048 UK18065

Modules/Macros

  •    DFHDSDUF
    

Fix information

  • Fixed component name

    CICSTS 3.1 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R400 PSY UK18065

       UP06/09/20 P F609

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":"3.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":"3.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
11 October 2006