IBM Support

PM02131: RECORD LEVEL SHARING RLS GENERIC DELETE RETURNS WRONG RIDFLD OR KEY IN DFHFC0165

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • RLS Generic Delete may return the wrong key when there is a wait
    on a record. Since CICS uses read update and delete for each
    record in the generic delete range RLS may report the first key
    outside the range if there is a wait and the wait either hits
    DTIMOUT or FTIMEOUT. The key reported in DFHFC0165 will not be
    in the range of records generically deleted.
    Additional Symptom(s) Search Keyword(s): KIXREVRHC
    

Local fix

  • The Generic Delete actually works in this case. However, if
    backoutonly is specified for the file then all the records that
    were deleted would be re-added.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend AFCV for a key beyond the         *
    *                      genus of an RLS file generic            *
    *                      delete.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A generic delete was issued for a VSAM RLS file. There happened
    to be another task holding the record lock for the next record
    that followed the range of records within the genus of the
    generic delete. DFHFCRS looped around the records within the
    scope of the deletion, issuing GET UPDATE and ERASE calls to
    VSAM RLS to delete them. It then issued a GET UPDATE for the
    first record beyond the genus of the generic delete. Normally
    this would return successfully, at which point DFHFCRS would
    detect that the record was beyond the range of the deletion,
    and the command would complete with a NORMAL response. In
    this case however, the record was locked to another task and
    so DFHFCRS had to issue an FCRVWAIT for it to become available.
    This eventually timed out, and the generic delete failed with
    messages DFHFC0164, DFHFC0165 and abend AFCV. This behaviour
    is inconsistent with the same set of events for a non-RLS
    file. In that case, the record lock would be acquired by CICS
    (not VSAM), and DFHFCVS would have noted the key was beyond
    the genus and so ended the generic delete before the record
    lock was acquired.
    KEYWORDS: abendAFCV msgdfhfc0164 fc0164 0164
              SMSVSAM   msgdfhfc0165 fc0165 0165
                        msgdfhfc6040 fc6040 6040
    

Problem conclusion

  • DFHFCRS has been modified to detect that a timeout took place
    for a record that was beyond the genus of a generic delete,
    and return NORMAL if this is the case. New informational message
    DFHFC6040 is issued to assist with any investigation.
      The CICS Transaction Server V4.1 Messages and Codes manual
    (GC34-7035-00) will be updated as follows. New message DFHFC6040
    will be added to Chapter 1, Page 504, after the entry for
    DFHFC6039:
    .
    DFHFC6040  I  DATE TIME APPLID  TIMEOUT PERIOD
              HAS EXPIRED PROCESSING A GENERIC DELETE AGAINST AN
              RLS FILE. THE TASK WAS WAITING ON A RECORD THAT
              WAS BEYOND THE GENUS OF THE GENERIC DELETE
              REQUEST. ONCE THE REQUEST HAD TIMED OUT, THE
              REQUEST COMPLETED AND THE TASK RESUMED NORMAL
              EXECUTION. FILE NAME  FILENAME . DATA SET NAME
               DSNAME .
    
    EXPLANATION:  A program has issued a generic delete
    command against an RLS file.  The request involves a series
    of get update and erase requests to VSAM to remove the
    records within the genus of the delete. When a record with a
    key outside the genus of the delete is encountered, the
    command completes. It is possible that this record is
    currently locked to another request. If this is the case,
    the generic delete waits for the other request to complete,
    or eventually will timeout. If it times out, CICS treats
    this as a successful completion of the generic delete
    operation, and the task resumes normal execution.
    
    The name of the file used is  filename . The data set is
     dsname .
    
    SYSTEM ACTION:  This is an informational message that
    identifies when a generic delete request against an RLS file
    is delayed for this particular reason. CICS continues
    processing.
    
    USER RESPONSE:  Investigate the other users of the file if
    appropriate.
    
    DESTINATION:  CSFL
    
    MODULE:  DFHFCRS
    
    XMEOUT PARAMETERS: date, time, applid,
    filename, dsname
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM02131

  • 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

    2009-11-26

  • Closed date

    2010-01-25

  • Last modified date

    2010-02-01

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

    PM00718

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

    UK53684

Modules/Macros

  • DESFCRS  DFHFCRS  DFHMEFCC DFHMEFCE DFHMEFCK
    DFH02131
    

Publications Referenced
GC34703500    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R600 PSY UK53684

       UP10/01/27 P F001

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:
01 February 2010