Rex, That is almost definitely it. We only allowed shr(3,3) in TEST CICS. Every once in a while a batch update to a file opened in CICS would get an abend and the file looked hosed. I had to close in CICS and reorg it, then re-oipen it. Bad practice.
I think they went to the H&W SYSB-II product after I left to resolve these type of issues. Best Regards, John Clifford On Tue, May 20, 2014 at 3:57 PM, Pommier, Rex <[email protected]>wrote: > John, > > I'm gonna chalk it up to application error. I (after the fact) just found > out this is actually defined to CICS. CICS puts records into this DS, then > apparently a batch job comes along and reads the records, writes them to > MQSeries, then deletes them off the DS. > > Rex > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of John McKown > Sent: Tuesday, May 20, 2014 3:26 PM > To: [email protected] > Subject: Re: VSAM question/problem > > 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 > > 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 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
