IBM Support

PM54820: FORCE CLOSE OF A FILE GOES INTO AN ENQUEUE WAIT WHEN USING SPI OR CEMT

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 Transaction server 4.1 and you are trying
    to FORCE close a file with an SPI or CEMT command. The file then
    goes into an Enqueue wait if there is an outstanding attempt to
    close a file.
    
    Here is one way to reproduce this problem:
    
    1) Use CECI to READ/UPDATE on a file.
    2) Issue an SPI call to do a SET FILE CLOSE on that file. The
    transaction with the SPI will go into an ENQUEUE wait with
    resource name being the file name.
    3) Issue a CEMT SET FILE FORCE.
    
    What is happening is that SET FILE requests for a file are
    single threaded at the EIP level by getting an ENQUEUE on the
    file name. In this case, this means that the SET FILE CLOSE
    requests get this ENQUEUE, and the SET FILE FORCECLOSE request
    is made to wait. The code to purge other tasks using the file
    does not get driven.
    
    Additional Symptom(s) Search Keyword(s):
    KIXREVEPH
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: EXEC CICS SET FILE CLOSED FORCE         *
    *                      requests are suspended behind other     *
    *                      SET FILE requests.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    EXEC CICS SET FILE requests are single threaded using an ENQUEUE
    at the EIP layer. This is done for all SET FILE requests, and
    means that commands specifying the FORCE option can be held up
    by other SET FILE commands already in the system. These
    pre-existing SET FILE commands may themselves be suspended, due
    to ongoing activity against the file, which means that the SET
    FILE command specifying the FORCE option is locked out.
    

Problem conclusion

  • DFHEIQDS has been updated so that the ENQUEUE is not requested
    for SET FILE CLOSED or DISABLED requests, which specify the
    FORCE option. Note that each of the keywords CLOSED, DISABLED,
    and FORCE, can also be specified using their equivalent CVDA
    values.
    
    
    The CICS Transaction Server for z/OS Version 4 Release 1 System
    Programming Reference (SC34-7024-02) will be updated in the
    description of the BUSY keyword on the SET FILE command.
    The first sentence will be changed to read:
    "Specifies the CICS action if the file is in use by CICS API
    requests when you issue the SET command."
    
    The FORCE option will be changed to read:
    "FORCE
    All API requests using the file abend, the file is immediately
    DISABLED or CLOSED, and control returns to the issuing
    application. SET FILE commands are single threaded, but with
    the FORCE option, the command runs without waiting for any
    other SET FILE commands to complete."
    
    The section starting 'Closing a file using the FORCE option'
    will be updated:
    "Closing a file using the FORCE option causes the tasks of any
    current applications using the file to be stopped immediately
    by the CICS task FORCEPURGE mechanism. Data integrity is not
    guaranteed with this mechanism. In some extreme cases (for
    example, if an error occurs during backout processing), CICS
    might end abnormally. For this reason, close files using the
    FORCE option only in exceptional circumstances."
    
    
    
    The CICS Transaction Server for z/OS Version 4 Release 1
    Supplied Transactions manual (SC34-7004-02) will be updated.
    The FORCECLOSE option of the CEMT SET FILE command will be
    updated in the first section to read:
    
    "FORCECLOSE
    Similar to SET FILE CLOSED, except that any existing API
    requests using the file are abended (abend code 'AKC3' or
    'ATCH'). As for CLOSED, the close is effected by the last of
    these users."
    
    
    
    The CICS Transaction Server for z/OS Version 4 Release 2 System
    Programming Reference (SC34-7186-01) will be updated in the
    description of the BUSY keyword on the SET FILE command.
    The first sentence will be changed to read:
    "Specifies the CICS action if the file is in use by CICS API
    requests when you issue the SET command."
    
    The FORCE option will be changed to read:
    "FORCE
    All API requests using the file abend, the file is immediately
    DISABLED or CLOSED, and control returns to the issuing
    application. SET FILE commands are single threaded, but with
    the FORCE option, the command runs without waiting for any
    other SET FILE commands to complete."
    
    The section starting 'Closing a file using the FORCE option'
    will be updated:
    "Closing a file using the FORCE option causes the tasks of any
    current applications using the file to be stopped immediately
    by the CICS task FORCEPURGE mechanism. Data integrity is not
    guaranteed with this mechanism. In some extreme cases (for
    example, if an error occurs during backout processing), CICS
    might end abnormally. For this reason, close files using the
    FORCE option only in exceptional circumstances."
    
    
    
    The CICS Transaction Server for z/OS Version 4 Release 2
    Supplied Transactions manual (SC34-7184-01) will be updated.
    The FORCECLOSE option of the CEMT SET FILE command will be
    updated in the first section to read:
    
    "FORCECLOSE
    Similar to SET FILE CLOSED, except that any existing API
    requests using the file are abended (abend code 'AKC3' or
    'ATCH'). As for CLOSED, the close is effected by the last of
    these users."
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM54820

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-21

  • Closed date

    2012-03-30

  • Last modified date

    2012-05-02

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

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

    UK77539 UK77540

Modules/Macros

  •    DFHEIQDS
    

Publications Referenced
SC34702402SC34718601SC34700402SC34718401 

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R600 PSY UK77539

       UP12/04/11 P F204

  • R700 PSY UK77540

       UP12/04/11 P F204

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

Document Information

Modified date:
02 May 2012