I don't know VSAMUTIL, but it likely looks at the catalog statistics. With VSAM, the catalog statistics are _NOT_ guaranteed to be correct. In fact, your LISTC has this warning it the listing:
STATISTICS (* - VALUE MAY BE INCORRECT) The only way to "fix" this is to delete/define/reload the data set. There is no way to reset the catalog statics any other way. The catalog statistics can become corrupted if a program has the data set OPEN for OUTPUT or UPDAT and then abends. In this case, the in-memory catalog statistics are not put in the catalog entry, and it is flagged as "not necessarily correct". So, in fact, no problem. Except with programs which assume that the statistics are "golden" and make decisions based on them, rather than actually reading the file itself. 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: > > -- There is nothing more pleasant than traveling and meeting new people! Genghis Khan Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
