IBM Support

PH14987: DEBUG PROFILE FILE DFHDPFMB DFHDPFMP FLOOD SYSLOG WITH DFHDP0100MESSAGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 1)  The start of this was the x27 DFHDP0100 message, when an
    update to a CADP profile failed for insufficient space in the
    AIX. This would have been a single problem (you would need
    to be trying to add a debug profile by means of using the
    CADP transaction). New transactions would start, drive DPXM
    INIT and DPXM BIND, and existing profiles would be
    pattern-matched against the new transactions to see if they
    should be debugged or not. No other problems would be seen.
    2) In closing the files in order to resolve the space problems
    with the sphere, CPSM closed them on the various CICS systems.
    This meant the running systems suddenly got a failure every
    time a new transaction got attached. DPXM would not be able
    to browse the file to see if a debug profile matched them.
    Each transaction would get a x20 DFHDP0100 failure. This was
    seen on all CICS systems using DEBUG.
    3) The flurry of these x20 DFHDP0100 failures, one per new
    transaction as it got attached, and in turn seen on all the
    CICS systems that were running with DEBUG active, meant the
    syslog message buffers struggled to cope with the volume of
    message data suddenly being generated.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: A DFHDP0100 message is issued every     *
    *                      time a CICS transaction begins.         *
    ****************************************************************
    The customer experienced a problem using CADP and updating their
    Debug Profile data sets due to insufficient index space.This led
    to message DFHDP0100 being issued for reason code x'27' (nospace
    condition). CPSM closed the files so that the data set space
    problem could be resolved. Since CICS Debug Profile support
    was still active, subsequent transaction attaches drove the
    DP domain for init and bind processing as before, and the
    attempted browse of the profile data sets failed with reason
    x'20' (file_not_open condition). This led to a DFHDP0100 message
    to report this for every CICS transaction being attached from
    this point onwards.
    KEYWORDS: MSGDFHDP0100 DP0100 0100 DEBUGTOOL DEBUG NODEBUG
    CICSPLEX x20 x27
    

Problem conclusion

  • DFHDPCM has been changed to deactivate Debug Profile support
    if a profile data set operation fails due to file_not_open
    being returned. Once the underlying data set problem has been
    resolved, CICS Debug Profile support can be reactivated by
    setting DEBUGTOOL(DEBUG) under CEMT or via the CICS SPI.
       The CICS TS Messages and Codes 5.4 manual will be
    updated as follows. In the explanation for message DFHDP0100,
    the explanation of reason code X'20' in the System Action
    section will be changed to state:
      "The file definition for the debugging profiles base data set,
    DFHDPFMB, or path data set, DFHDPFMP, cannot be opened. Examine
    the console to find file control or VSAM messages that will
    indicate the reason for the error. Note that Debug Profile
    support is deactivated following a file not open response."
      The User Response will be changed to state:
      "Investigate and correct the error based on the reason given
    and retry. In the case of an X'20' (FCFR_FILE_NOT_OPEN) reason
    code, once the underlying data set problem has been resolved,
    CICS Debug Profile support can be reactivated."
      The same change will be made to the CICS TS 5.5 Messages and
    Codes manual.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH14987

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-26

  • Closed date

    2019-09-30

  • Last modified date

    2019-11-01

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

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

    UI65575 UI65576

Modules/Macros

  • DFHDPFM  DFHDPLM  DFHDPUM  DFHMEDPE
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R100 PSY UI65576

       UP19/10/02 P F910

  • R200 PSY UI65575

       UP19/10/03 P F910

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

Document Information

Modified date:
01 November 2019