IBM Support

PH26064: INVREQ RESP2(45) WHEN OPENING DELETED AND REDEFINED QUIESCED DATASET 20/06/04 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ERROR DESCRIPTION:
    Your CICS region has the ptf for APAR PH13588 applied and you
    have successfully quiesced a dataset. This turns the FCTDNQUI
    bit on (indicating a data set is quiesced or found to be
    quiesced).  After it is quiesced it is then deleted and
    redefined. When you then try to OPEN the File associated with
    that dataset in CICS it fails with a Resp2 code of 45:
    DFHAP1900 SET FILE(FILENAME) OPEN RESP(INVREQ) RESP2(45)
    The 45 indicates that:
    45 A file open request cannot be satisfied because the file
    references an RLS-mode data set that was quiesced by a SET
    DSNAME QUIESCED command.
    The delete and redefine reates a new version of the dataset to
    VSAM and the new version of the data set is created as
    unquiesced. There is no attempt to inform RLS (or its
    CICS clients) that the work has completed by means of an
    unquiesce command. If this were issued, CICS would be called,
    turn off FCTDNQUI, and all would be well.
    This fix will ensure that dynamically deallocated data sets
    have the flag turned off when closing their files in CICS and
    when an EXEC CICS INQUIRE DSNAME command is issued and VSAM
    returns the fact the data set is now unquiesced. Without an
    unquiesce command being explicitly issued, CICS cannot know
    that the data set has been redefined under its feet like this.
    So it does require either using an unquiesce, or using the
    INQUIRE SPI to know it is time to issue opens from within CICS
    again.
    Additional Symptom(s) Search Keyword(s): INVREQ , FCTDNQUI
    KIXREVxxx
    

Local fix

  • Issue an unquiesce command at the end of file processing
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users with PH13588 applied.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Opens of RLS files fail with            *
    *                      INVREQ when their associated data       *
    *                      sets are no longer quiesced.            *
    ****************************************************************
    The customer quiesced their data set and CICS closed the
    associated RLS file. The data set was deallocated as part of
    this close. CICS remembered the data set was quiesced by flag
    FCTDNQUI being set in the DSNB. It is expected that after the
    user has performed their work on a quiesced data set, an
    unquiesce command be sent to have RLS inform CICS that the
    data set is no longer quiesced, at which time CICS will turn off
    FCTDNQUI. However, the customer chose to end the work with a
    delete and redefine of the data set. Since the default for the
    IDCAMS define cluster step is RLSENABLE, this recreates the
    data set in an unquiesced state. There is no mechanism for
    RLS to alert CICS that this has happened. This meant that when
    the customer attempted to open the RLS file against the data
    set after this point, the open failed with INVREQ as CICS
    still believed the data set was quiesced.
      The problem has been seen both for customers manipulating
    their data sets directly, and by the use of the CA DADS plus for
    CICS product.
      Note that the IDCAMS define step could have specified
    RLSQUIESCE instead, which would have rebuilt the data set in a
    quiesced state, and so mandated an unquiesce command before it
    could be reused by CICS. This is recommended by VSAM to keep
    the RLS quiesce state held by CICS in sync with the catalog,
    i.e. to redefine a data set back in a state that is consistent
    with its last state as known by CICS.
    
    
    KEYWORDS: SMSVSAM
    

Problem conclusion

  • UI65863  UI65864  UI65865
    CICS has been changed to ensure that FCTDNQUI is set off when a
    close of a file deallocates an associated data set, and when an
    EXEC CICS INQUIRE DSNAME command returns unquiesced for the
    status of a data set.
      CICS has also defined new trace point FC 233C to report
    FCQI_TRACE_LMLM_FAILED events for first failure data capture.
      Note - having performed whatever work is to be done against a
    quiesced data set, it is expected that an unquiese command be
    issued to ensure RLS can inform its clients that the data set is
    no longer quiesced.
      If an unquiesce command is not used at the end of the work,
    it is necessary for an EXEC CICS INQUIRE DSNAME to be
    issued after the data set has been redefined in this way, to
    ensure CICS can know the data set is no longer quiesced to RLS.
      The CICS TS System Programming Reference and CICS TS Supplied
    Transactions manuals for 5.3 and above will be updated as
    follows. In the section for SET DSNAME commands, a new paragraph
    will be added to the end of the description section:
    "Note:
    If data sets are quiesced in order to perform work outside of
    RLS, then when this is completed you should unquiesce the data
    sets to make RLS inform CICS that they are no longer quiesced.
    It is possible that a data set is redefined while quiesced.
    Redefining a data set takes it out of a quiesced state by
    default, but without an explicit unquiesce command CICS is not
    notified that the data set is no longer quiesced to RLS."
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH26064

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-03

  • Closed date

    2020-06-29

  • Last modified date

    2020-08-03

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

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

    UI70305 UI70306 UI70307 UI70308

Modules/Macros

  • DFHAPTR5 DFHDSND  DFHDTLX  DFHEIFC  DFHEIQCF DFHEIUOW DFHFCAT
    DFHFCBD  DFHFCBU  DFHFCCA  DFHFCDL  DFHFCDN  DFHFCDO  DFHFCDR
    DFHFCDTS DFHFCDTX DFHFCDU  DFHFCDUF DFHFCDW  DFHFCDY  DFHFCES
    DFHFCFL  DFHFCFR  DFHFCFS  DFHFCIR  DFHFCL   DFHFCLF  DFHFCLJ
    DFHFCM   DFHFCMT  DFHFCN   DFHFCNQ  DFHFCOR  DFHFCQI  DFHFCQR
    DFHFCQS  DFHFCQT  DFHFCQU  DFHFCQX  DFHFCRC  DFHFCRC2 DFHFCRD
    DFHFCRF  DFHFCRL  DFHFCRN  DFHFCRO  DFHFCRP  DFHFCRR  DFHFCRS
    DFHFCRV  DFHFCSD  DFHFCST  DFHFCU   DFHFCVC  DFHFCVR  DFHFCVS
    DFHFCXDF
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI70308

       UP20/07/01 P F006 ­

  • R100 PSY UI70306

       UP20/06/30 P F006 ­

  • R200 PSY UI70305

       UP20/06/30 P F006 ­

  • R300 PSY UI70307

       UP20/07/03 P F007 ­

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.3","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
05 August 2020