APAR status
Closed as canceled.
Error description
THIS APAR HAS BEEN CREATED TO DOCUMENT: (for DFSMS users only) (for lower levels of DFP see II02490) last update 2/96 lsk 1. HOW TO DETERMINE WHICH DATA SET MAY BE CORRUPTED. 2. HOW TO ANALYZE, VERIFY AND GET DETAILS OF THE DAMAGE. 3. RECOVERY PROCEDURES FOR RESTORING A DAMAGED KSDS (FOR NONSPANNED RECORD, NON COMPRESSED DATASETS ONLY). 4. SYMPTOMS THAT CAN RESULT FROM A BROKEN INDEX COMPONENT OF A VSAM KSDS. 5. MAINTENANCE: VSAM PTFS, VSAM PE PTFS AND NON-VSAM APARS ASSOCIATED WITH DATA SET DAMAGE. 6. NON-CODE RELATED REASONS FOR DATA SET DAMAGE. 7. PROCEDURES TO DOCUMENT DATA SET SHARING PROBLEMS. 8. USER ERRORS THAT LOOK LIKE DATA SET DAMAGE. 9. PUBLICATIONS: FOR FURTHER INFORMATION SEE : 'ACCESS METHOD SERVICES for INTEGRATED CATALOG FACILITY' 'MACRO INSTRUCTIONS for DATA SETS' .... 'USING DATA SETS' (SHARING VSAM DATA SETS) .... 'DFP DIAGNOSIS REFERENCE' (RECORD MANAGEMENT DIAGNOSTICS) THIS APAR APPLIES TO THE FOLLOWING COMPIDS/FMIDS: DFSMS 5695DF105 5695DF106 JDZ1110 (R110) HDZ11B0 (R1B0) HDZ11C0 (R1C0) HDZ11D0 (R1D0) HDZ11E0 (R1E0) ************************************************************* ** 1. HOW TO DETERMINE WHICH DATA SET MAY BE CORRUPTED ** ************************************************************* 1) Symptoms with current PSW --> IDA019L1 load module: If the user has a dump resulting from an ABEND0C4 in the IDA019L1 load module, or a console dump of a LOOP or WAIT in IDA019L1, The data set component name (DSN) of the suspected cluster is found in the area pointed to by REG3. GR03 points to the AMB. An AMB begins with CBID('40'). At X'88' into the AMB (AMBDSNM) the data set component name is stored. 2) Symptoms external to VSAM processing: For users who suspect a WAIT or LOOP in VSAM, but without registers current while IDA019L1 was processing, the AMB can be found from the RPL. RPL + x'18' points to the ACB. ACB+4 points to the AMBL. The AMBL + x'34' points to the AMB. The AMB + x'88' is where the DSNAME is stored. **************************************************************** ** 2. HOW TO ANALYZE, VERIFY AND GET DETAILS OF THE DAMAGED ** ** DATA SET (FOR NONSPANNED RECORD KSDS DATASETS ONLY) ** **************************************************************** Execute the IDCAMS EXAMINE INDEXTEST and DATATEST preceeded by VERIFY to open and close data set. EXAMPLE is shown below. Save all the output. Also run LISTYCAT. If the damaged cluster can be saved using a FULL VOLUME DUMP, or the DATASET DUMP, or TRACK DUMP, then it may be useful in analyzing the cause of the problem. EXAMPLE of IDCAMS JCL commands follow: ------------------------------------------- //SYSIN DD * VERIFY DATASET(IBMUSR1.ISPFDIR) LISTC ENT(IBMUSR1.ISPFDIR) ALL EXAMINE NAME(IBMUSR1.ISPFDIR) ITEST NODTEST EXAMINE NAME(IBMUSR1.ISPFDIR) DTEST NOITEST PRINT INDATASET(IBMUSR1.ISPFDIR.INDEX) DUMP /* **************************************************************** ** 3. KSDS RECOVERY PROCEDURE FOLLOWS ** ***** THIS METHOD IS NOT FOOLPROOF; ******** ************* IT MAY RESULT IN MISSING RECORDS *************** **************************************************************** Example: The following VSAM KSDS cluster is damaged and we wish to recover the data. Cluster and component names are: IBMUSR1.ISPFDIR IBMUSR1.ISPFDIR.INDEX IBMUSR1.ISPFDIR.DATA 1. REPRO the .DATA component ONLY to a sequential file. REPRO INDATASET(IBMUSR1.ISPFDIR.DATA) OUTFILE(outdsname) 2. Using a sort package (DFSORT), sort this data file by KEY. Note: If your dataset contains duplicates then delete duplicates with DFSORT command : SUM FIELDS=NONE Caution: VSAM starts counting field positions at 0 while DFSORT starts counting at 1. 3. DELETE and reDEFINE the original dataset. 4. REPRO the data back in (this will rebuild the KSDS INDEX). NOTE: This previous recovery routine is used to recover a GOOD data component. It assumes that user has run ITEST and this INDEX test has produced negative results. Basically, the KSDS index is broken, but the data is OK. If the KSDS data component is BROKEN, then the best recovery procedure is to do forward recovery from a back up copy. Otherwise a user can jump/skip past the bad data records and recover those records that can be properly read (some data loss is expected). NOTE: Spanned datasets are not recoverable in this manner. At this time, REPROing the data component of a compressed dataset is not supported. ************************************************************* ** 4. SYMPTOMS THAT CAN RESULT FROM A BROKEN DATA SET ** ************************************************************* Any physical I/O errors, resulting in an RPL feedback word of 000C00xx (rcC rc12) almost always mean the dataset is broken. MSGIDC3302I ACTION ERROR MSGIDC3308I DUPLICATE RECORD MSGIDC3314I OUT OF SEQUENCE RECORD, OUTOFSEQ, MISSING RECORDS, MISSREC, DUPLICATE RECORDS, DUPREC MSGIDC3351I VSAM IO RC32 , RC24 , RC156 SENSE=0009 IMPRECISE END SENSE=0004 FILE PROTECT SENSE=0008 NO RECORD FOUND SENSE=0040 TRACK FORMAT I/O errors 86-OP READ and WRITE failures MSGIDC3350I NO RECORD FOUND, NRF, INCORRECT LENGTH MSGIEC070I RC32 , RC202 , RC8 , RC18 , RC24 , RC104 , RC203 MSGIEA000I MSGIOS000I CMD REJ, COMMAND REJECT MSGADR970E HSM MISSING CI within SEQUENCE SET TRACK TRACKS TRK TRKS TRKS=0 TRACKS=0 EXTENT Any physical I/O errors, resulting in an RPL feedback word of 000C000x rcC rc12 IDCAMS EXAMINE COMMAND MAY GIVE THE FOLLOWING MESSAGES: MSGIDC01714I ERROR LOCATED at OFFSET xxx MSGIDC01720I INDEX CONTROL INTERVAL DISPLAY at RBA xxx FOLLOWS MSGIDC11703I DUPLICATE KEYS in INDEX MSGIDC11704I INDEX KEYS are NOT in SEQUENCE MSGIDC11705I INDEX RECORD CONTAINS DUPLICATE INDEX POINTERS MSGIDC11707I DUPLICATE INDEX POINTERS FOUND in SEQUENCE SET MSGIDC11711I INDEX CONTROL INTERVAL COUNT ERROR MSGIDC11715I INDEX HIGH-USED RBA is NOT a MULTIPLE of CI SIZE MSGIDC11724I DATA COMPONENT CA NOT KNOWN to SEQUENCE SET MSGIDC11725I SEQUENCE SET RBA INCONSISTENT with VSAM- MAINTAINED RBA MSGIDC11727I INDEX HIGH-USED RBA GREATER THAN HIGH-ALLOCATED MSGIDC11728I DATA FOUND in EMPTY CI MSGIDC11733I DATA COMPONENT KEY SEQUENCE ERROR MSGIDC11758I SOFTWARE EOF FOUND in INDEX CI MSGIDC11763I RBA of INDEX CI GREATER THAN HIGH-USED RBA MSGIDC11771I INVALID RBA GENERATED MSGIDC11772I HORIZONTAL POINTER CHAIN LOOP ABEND0C4 IN ANY OF THE FOLLOWING MODULES: IDA019RC IDA019RE IDA019RG IDA019RH IDA019RF IDA019RI IDA019RJ IDA019RN IDA019RW IDA019R4 IDA019SD LOOPING ( LP ) ISSUING SVC121 HEX SVC79 0A79 svc x'79' LOOPING IN THE FOLLOWING VSAM MODULES: IDA019RB IDA019RC IDA019RE IDA019RH IDA019RZ IDA019RI IDA019RJ IDA019RN IDA019RW IDA121A4 IDA019R2 IDA019R3 IDAM19R3 IDA019RA LOOPING LOOP SIO STARTIO (DOING DFHSM MIGRATE or DB2 RECOVERY) SYSTEM 'HANG' with TCB STRUCTURE indicating WAIT in IDAM19R3, IDA019R3 or DFHSM 'HUNG' WAIT ISSUED FROM IDA019RZ (ws) (0A01) THE FOLLOWING RPL FEEDBACK WORD, RPLFDBWD, RPLERRCD: 2D08009C 9208009C A608009C A708009C DEC RC156 9108009C D708009C D808009C E008009C RC8 RC08 RC9C 2A080020 2C080020 DB080020 DF080020 RC20 DEC RC32 ************************************************************* ** 5. MAINTENANCE : ** ** TO FIND FIXES ASSOCIATED WITH BROKEN VSAM DATASETS ** ** USE THE SEARCH WORD 'DSBREAKER' IN EITHER RETAIN ** ** OR THRU IBMLINK (ASKQ). ** ** NOTE: RESEARCH PTFS OR APARS FOR ANY PE STATUS ** ** CHANGES BEFORE APPLYING. ** ** NOTE: VSAM LOADMODS IDA019L1 AND IDA0192A RESIDE ** ** IN SYS1.LPALIB . IN AS SUCH, ANY UPDATE TO ** ** ANY CSECT OF THESE LOADMODS WILL REQUIRE AN ** ** IPL CLPA TO FACILITATE REFRESH. ** ************************************************************* Due to space limitations the recommended maintenance for R1D0 and R1E0 can be found in II11955. ************************************************************* Here are PTFs that fix problems known to cause dataset breakage. R110 R1B0 R1C0 IDA019RY/IDA019SY UW13554 UW13553 UW33722 IDA019RE/IDA019R2 UW09009 UW09008 UW47514 IDA019RH UW47514 IDA019RW UY93392 UW25973 UW24338 IDA019SE UW15025 UW15024 IDA019R4 UW28698 IDA019S8 UW30892 UW30894 IDA019RT UW16288 UW16287 IDA019SA UW23521 UW23519 UW23520 IDA019SZ UW36508 IGG0CLFI UW33616 IGG0CLE5 UY95469 IDA0200T UW14318 UW14317 IDA0231B UW57010 IDA0192A UW50703 IDA0192B UW30892 UW58996 IDA0192C UW32589 UW32587 UW59992 IDA0557A UW16218 IDA0557B UW14698 UW14697 UW59992 IDA0557X UW59992 IDAVCCMS UW23621 UW23622 IDAXIRAR UW25571 ICYSORT UW23867 UW23868 ICYPFCP UW14274 ICYMMSRV UW23934 ICYRBA UW16659 IDA121A3 UW07644 UW07643 IDAEFSIO UW27522 UW27523 IGG0CLEX UW35297 UW35295 UW35296 -- NON-VSAM APARS ASSOCIATED WITH DATA SET DAMAGE -- ------------------------------------------------------------- HSM OY58428 Audit Mediacontrols HSM OY62721 Corrupted OCDS HSM OW17044 Corrupted MCDS HSM OW05969 Corrupted DB2 LDS (OEM ERR) ERP OW02559 This can cause corruption on any type dataset. DOC OY13875 Invalid / small INDEX cisize definition DSS OW06277 KSDS INDEX DAMAGE R120 / R1B0 (R502 PN56661) DSS OW06418 KSDS INDEX DAMAGE R120 / R1B0 (R502 PN59386) DSS OW06503 DSS KSDS INDEX WITH IMBED CORRUPTED (PN59709) DSS OW10586 DSS KSDS INDEX WITH IMBED CORRUPTED (PN62581) DSS OW17877 Taken to provide a way to backup file that have a minor error in the index component. Examine will give MSGIDC11724I DATA COMPONENT CA NOT KNOWN TO SEQUENCE SET The file is not really broken. For more information see VSAM apar OW18171 . DSS OW36919 DEFRAG moves datasets that are open. DSS OW37826 DEFRAG moves datasets that are open. HARDWARE RAMAC HSF tip H13517 - after sparing, predictive track table is not updated correctly. Turn device caching off and back on will correct the errors. Wide spread symptoms. various examine errors and IDC3350i 86-op, Track Format or Imprecise End or No Record Found NRF , etc. ************************************************************* ** 6. NON-CODE RELATED REASONS FOR DATA SET BREAKAGE ** ************************************************************* 1. Sharing a data set across regions (CROSSREGION) or across systems (CROSSSYSTEM) without using proper ENQuing procedures to protect data set integrity. Shareoptions SHR(3 3) SHR(4 3) SHR(3 4). See also, related information in OY36328. *** INFO/SYS USERS *** INFO SYSTEMS DATABASES ARE CREATED WITH SHR(3 3). SEE INFO/SYS INSTALLATION GUIDE (SC34-4046) PG 1-2 FOR REQUIRED ENQUEUE RESOURCE NAMES. 2. Sharing a data set across systems without propagating SYSVSAM around the GRS ring. This is the *MOST* common user error and will result index and/or data corruption. The most common error being duplicate pointers in the high level index records. Specifically: MSGIDC11705I INDEX RECORD CONTAINS DUPLICATE INDEX POINTERS
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
close for Internet viewing
APAR Information
APAR number
II08859
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1995-08-09
Closed date
1997-11-07
Last modified date
2019-12-10
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
10 December 2019