IBM Support

OA59381: SMSVSAM BROKEN INDEX WHILE PERFORMING MULTIPLE DELETES AT SAME TIME WITH CARECLAIM ACTIVE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If multiple mass deletes are issued against a RLS data set with
    CARECLAIM active at the same time there is a timing window where
    CARECLAIM may corrupt the 2nd level index record causing request
    to loop.
    
    An examine of the data set will show following errors:
    INDEXTEST:
    IDC11726I CI ON CURRENT LEVEL NOT POINTED TO BY NEXT LEVEL
    
    DATATEST:
    IDC11772I HORIZONTAL POINTER CHAIN LOOP
    
    This fix will prevent the data set corruption and apar OA59403
    will add protection against the loop caused by processing with a
    corrupted index.
    
    Additional keywords:
    DIWA Loop
    RLSLOOP RLSCPU
    SMSVSAM RLS VSAMRLS DF122
    RLSPSP/K
    

Local fix

  • BYPASS/CIRCUMVENTION:
    A close of file and/or shutdown of regions using it
    
    RECOVERY ACTION:
    Rebuild index, or recover data set
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL VSAM RLS USERS.                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * INDEX CORRUPTION OCCURS IN A KSDS AFTER                      *
    * PROCESSING SIMULTANEOUS CA RECLAIMS.                         *
    * EXAMINE ERROR MSGIDC11726I AND/OR                            *
    * IDC11774I REPORTS THE DAMAGE OR BREAK.                       *
    * SEQUENTIAL REQUESTS DIRECTED AT THE                          *
    * CORRUPT FILE MAY RESULT IN INFINITE                          *
    * LOOPING.                                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A SMALL TIMING WINDOW EXISTS WHEREIN IF 2 CA RECLAIMS ARE
    OCCURRING SIMULTANEOUSLY IN THE SAME KSDS, AND THE 1ST 2ND LEVEL
    INDEX RECORD IS DIRECTLY PREVIOUS TO 2 2ND LEVEL INDEX RECORDS
    BEING RECLAIMED, THE HORIZONTAL POINTER OF THE 1ST 2ND LEVEL
    INDEX RECORD IS NOT UPDATED. THE RESULT IS INDEX COMPONENT
    CORRUPTION AND A BROKEN HORIZONTAL CHAIN.
    

Problem conclusion

  • LOGIC IS CORRECTED TO ENSURE ALL UPDATES MADE TO INDEX RECORDS
    DURING CA RECLAIM ARE PROPERLY MADE.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    OA59381

  • Reported component name

    VSAM REC LEV SH

  • Reported component ID

    5695DF122

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-06

  • Closed date

    2020-04-13

  • Last modified date

    2020-06-01

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

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

    UJ02619 UJ02620 UJ02654

Modules/Macros

  • IDAVRSG0
    

Fix information

  • Fixed component name

    VSAM REC LEV SH

  • Fixed component ID

    5695DF122

Applicable component levels

  • R240 PSY UJ02620

       UP20/05/19 P F005 ¢

  • R230 PSY UJ02619

       UP20/05/19 P F005 ¢

  • R220 PSY UJ02654

       UP20/05/19 P F005 ¢

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020