IBM Support

PH29870: DFHFC0002 A SEVERE ERROR (CODE X'2424') HAS OCCURRED IN MODULE DFHFCRO

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You are running CICS TS 5.2 and receive the following
    Error Messages:
    DFHFC0952  Dynamic allocation of RLS file FILEA failed.
               Return code X'0004',X'0210' in module DFHFCRO.
    DFHFC0955  Associated data set is AAAAA.BBBB.FILEA  Module
               DFHFCRO.
    DFHFC0977  RLS OPEN of file FILEA failed. VSAM catalog error.
               Return code - X'8114',X'0032' in module DFHFCRO.
    DFHFC0002  A severe error (code X'2424') has occurred in
               module DFHFCRO.
    
    Dynalloc  fails with RC 4 reason x'0210' because the file is
    currently open to the batch job.
    Manual intervention is needed to open FILEA.
    
    Additional symptoms: KIXREVxxx
    unquiesce file left Closed Unenabled.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: NOTOPEN is returned on a RLS FILE       *
    *                      that has been unquiesced.               *
    ****************************************************************
    An RLS file is in CLOSED ENABLED state. It was then opened, so
    put in OPEN ENABLED state. It was then closed by a quiesce of
    its associated data set, so became CLOSED UNENABLED. This was
    followed by an unquiesce, and CICS reenabled the file (to
    CLOSED ENABLED state) to allow a subsequent CICS file API
    command to implicitly reopen the file. Before this took place
    however, another quiesce of the data set was issued. Since the
    file was not open this time, no quiesce processing had to be
    performed by DFHFCQU, and in particular FCTUQENA was not set in
    the FCT to ensure that a subsequent unquiesce would reset the
    file to ENABLED state.
      While the file was now CLOSED UNENABLED, a timing race took
    place between an API command issued against the file (and so
    CICS trying to reopen it), and a batch program which wanted to
    delete and redefine the quiesced data set before unquiescing
    it.
      The file open processing in DFHFCRO issued a DYNALLOC of the
    data set and this failed with message "DFHFC0952 - Dynamic
    allocation of RLS file  failed. Return code X'0004',X'0210'
    in module DFHFCRO". This was because the batch job now owned
    the data set and it could not be allocated to CICS.
      DFHFCRO proceeded to issue a LOCATE against the data set
    as part of related open processing logic. This failed with
    message "DFHFC0977 - RLS OPEN of file  failed. VSAM catalog
    error. Return code - X'8114',X'0032' in module DFHFCRO." This
    was because the batch job had now deleted the data set and
    catalog services could not complete the LOCATE SVC26 call
    successfully.
      DFHFCRO left the file in CLOSED UNENABLED state as a result
    of these errors.
      The batch job completed redefining the data set and used
    EXCI to drive CICS to unquiesce it.
      Since FCTUQENA had not been set in the FCT at the time of the
    quiesce, this left the file CLOSED UNENABLED, as unquiesce
    processing did not reset the file status to ENABLED.
      File control API requests against the file now failed with
    NOTOPEN. The file had to be manually re-enabled to allow them
    to reopen the file and succeed.
    KEYWORDS: msgDFHFC0952 fc0952 0952 952
              msgDFHFC0977 fc0977 0977 977
    

Problem conclusion

  • DFHFCRO has been changed to ensure that FCTUQENA is set on
    if a DYNALLOC failure occurs, to ensure that a file in this
    state (that has been opened and closed in the past) is
    re-enabled on a subsequent unquiesce of its data set.
      Note that a file which had yet to be opened before being
    quiesced and unquiesced would not have been associated with the
    underlying DSNB by this point (it would yet to have been added
    to the active FCTE chain as part of a file open) and so an
    unquiesce would not be able to locate the FCT in order to check
    for FCTUQENA and re-enable the file state. To avoid this variant
    of the problem, a customer could use the EXEC CICS INQUIRE
    DSNAME SPI to determine the availability of a file, by checking
    whether its data set was quiesced or not, before attempting
    file control API operations against it.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH29870

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-24

  • Closed date

    2020-12-08

  • Last modified date

    2021-01-04

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

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

    UI72975 UI72976 UI72977 UI72978 UI72979

Modules/Macros

  • DFHFCRO
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI72978

       UP20/12/10 P F012

  • R100 PSY UI72977

       UP20/12/09 P F012

  • R200 PSY UI72976

       UP20/12/09 P F012

  • R300 PSY UI72975

       UP20/12/11 P F012

  • R900 PSY UI72979

       UP20/12/11 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.

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2"}]

Document Information

Modified date:
05 January 2021