John C., REPRO'ing with the REUSE reset the statistics and did the mini reorg. This leads me to further believe there was an application hiccup that caused the problem in the first place. I can't say for sure, but my guess is there's something 'not-quite-right' in the enqueueing logic that is supposed to be protecting the dataset from being updated by CICS and batch simultaneously.
Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Clifford Sent: Tuesday, May 20, 2014 3:55 PM To: [email protected] Subject: Re: VSAM question/problem Rex, Have you tried using REPRO (IDCAMS) to unload it to a flat file (vb/9160/27998) and see if it goes clean or issues an error message which may be more informational. If no error, try to repro 'reuse' back over the file with the unloaded record. Being there are some counts in the splits field, there has to have been a bunch more records. See if this mini reorg fixes it. John Clifford IBM consultant On Tue, May 20, 2014 at 2:17 PM, Pommier, Rex <[email protected]>wrote: > Hi List, > > We have a VSAM KSDS with 1 record in it that is causing us some heartburn. > I was able to create a new dataset and REPRO this one into the new one > successfully, and the new dataset works fine, but I'd like to know what may > be causing the original to be having problems - and possibly how to fix it. > It is not open to any online regions, but is used by batch. A LISTC of > the dataset shows bogus statistics - even after running a VERIFY against it > (which came back clean, RC=0). I ran an EXAMINE against it and got no > errors: > > EXAMINE NAME(LFCT.MQ.BPX.BILLCASE.MASTER) DATATEST > IDC01700I INDEXTEST BEGINS > IDC11773I 1 KEYS PROCESSED ON INDEX LEVEL 1, AVERAGE KEY > LENGTH: 0.0 > IDC11774I CURRENT INDEX CISIZE IS 1024, RECOMMENDED MINIMUM INDEX CISIZE > IS 1024 > IDC01724I INDEXTEST COMPLETE - NO ERRORS DETECTED > IDC01701I DATATEST BEGINS > IDC01709I DATATEST COMPLETE - NO ERRORS DETECTED > IDC01708I 1 CONTROL INTERVALS ENCOUNTERED > IDC01710I DATA COMPONENT CONTAINS 1 RECORDS > IDC01711I DATA COMPONENT CONTAINS 0 DELETED CONTROL INTERVALS > IDC01712I MAXIMUM LENGTH DATA RECORD CONTAINS 333 BYTES > IDC01722I 99 PERCENT FREE SPACE > IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 > > We have 2 VSAM utility programs, VSAMTUNE and VSAMUTIL. VSAMTUNE says the > dataset is fine and displays the record: > > Cluster LFCT.MQ.BPX.BILLCASE.MASTERB > Catalog CATALOG.MVSICF1.VADR111 > Rcd len 00333, rcd RBA 0000000000023000, key length 030, key offset 00000. > > > VSAMUTIL however, says the dataset is empty. > > "THIS DATASET CONTAINS NO RECORDS, USE EDIT TO LOAD" > > > Unfortunately I don't have any diagnostic codes out of the COBOL program > that was getting the open error. > > > > So my question - any idea what could be broken in this dataset to cause > this kind of problem (bogus stats that I can't fix and some programs not > being able to open the dataset/find the record in it)? > > TIA for any pointers. > > Rex > > > > Here's the LISTC of it (with some parts removed to conserve reading > time..). > The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
