IBM Support

PM22668: MESSAGE DFHFC0002 A SEVERE ERROR (CODE X'2326') HAS OCCURRED IN MODULE DFHFCQU ISSUED BECAUSE OF TIMING PROBLEM

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Message DFHFC0002 A SEVERE ERROR (CODE X'2326') HAS OCCURRED IN
    MODULE DFHFCQU was issued because of timing issue.
    Task A was attempting to open a VSAM RLS file, this has failed.
    At the same time task B has issued a
    FUNCTION(PROCESS_QUIESCE) QUIESCE_TYPE(UNQUIESCE) call.
    This unquiesce call has failed against the dataset because the
    corresponding file is being processed by another task.
    Task B was trying to unquiesce dataset.
    So both task A and task B are trying to work with the
    same file and in all likelihood the two tasks are interleaving.
    .
    The trace for task B also shows that the FCFS request that
    led to this exception was a FILE_ENABLE request and this
    request has returned FILE_DISABLING. Firstly for DFHFCQU to
    call FILE_ENABLE, then the file must have been disabled due to
    a close request (FCTDSIMP = on), been set to be re-enabled on a
    QUIOPEN (FCTUQENA = on)  and have no close requests outstanding
    (FCTDSCRQ = off). However once DFHFCFS had been called and
    taken control, it would have discovered that another
    task (task A) had outstanding activity against the file (has a
    FLAB and FCTE pointing at the file's FCT).
    This prevents file_enable completing and therefore prevents the
    unquiesce completing.
    So to summarise, this is a timing problem.
    Change team discussed with development and they agreed that a
    new message that is accompanied by a transaction abend would be
    appropriate. This new message would be able to indicate
    which dataset needs to be manually unquiesced and if this new
    message was issued persistently then the customer could take a
    system dump in place of the transaction dump to be looked at by
    support.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Unquiesce failure results in            *
    *                      DFHFC0002.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An attempt was made to unquiesce a dataset but the same dataset
    was in use by another task, CICS issued severe error message:
    
    DFHFC0002 A SEVERE ERROR (CODE X'2326')
    HAS OCCURRED IN MODULE DFHFCQU.
    
    A WARNING message would have been sufficient.
    
    Keywords: FC0002 msgDFHFC0002 2326
    

Problem conclusion

  • DFHFCQU has been amended to issue a new warning message of
    DFHFC6041 when a task attempts an unquiesce of a dataset which
    is in use by another task.
    
    
    In publication GC34-6827-03, CICS Transaction Server for z/OS
    Messages and Codes Version 3 Release 2
    -> Chapter 1 DFH messages
    -->  DFHFCnnnn Messages
    
    After message DFHFC6040 on page 470, the following new message
    will be added DFHFC6041 as per DFHFC6040 with the following
    text:
    
    DFHFC6041  W "DATE TIME APPLID" ATTEMPT TO
              UNQUIESCE DATA SET "DSNAME" FAILED DUE TO A
              CONFLICT WITH ANOTHER TASK.
    
    EXPLANATION:  An attempt by CICS to unquiesce data set
    "dsname" has failed because of a conflict with another
    task attempting to use the same data set.
    
    SYSTEM ACTION:  CICS processing continues.  The quiesce
    state of the data set is unpredictable.
    
    USER RESPONSE:  Try the unquiesce request again by issuing
    an EXEC CICS SET DSNAME or the CEMT equivalent command
    specifying the UNQUIESCE option to set the quiesce state of
    the data set in the ICF catalog to unquiesced.
    
    If the problem persists, a more severe error has occurred.
    Change the dump table to take a system dump on this message
    and contact IBM for assistance.  See Part 4 of the "CICS
    Problem Determination Guide" for guidance on how to
    proceed.
    
    DESTINATION:  Console and Transient Data Queue CSFL
    
    MODULE:  DFHFCQU
    
    XMEOUT PARAMETERS: date, time, applid,
    dsname
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM22668

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-09-16

  • Closed date

    2010-12-17

  • Last modified date

    2011-01-03

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

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

    PM23268 UK63272

Modules/Macros

  •    DESFCQU  DFHFCQU  DFHFCTRM DFHMEFCC DFHMEFCE
    DFHMEFCK DFH22668
    

Publications Referenced
GC34682703    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R500 PSY UK63272

       UP10/12/30 P F012

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

Document Information

Modified date:
03 January 2011