First off, thanks for all who chimed in with ideas. Here's what we found out.
We're checking with the developers to see if they have any reason this VSAM dataset needs to be SHR(3 3), with the recommendation they change it to (2 3). The batch code has no internal means of serializing updates to guarantee integrity. This was a test of some new functionality that is supposed to be only running while CICS is down, but the developer decided to test it during the day while the VSAM DS was open to CICS. Again, thank you for assisting. Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Clark Morris Sent: Tuesday, May 20, 2014 8:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: VSAM question/problem On 20 May 2014 14:25:42 -0700, in bit.listserv.ibm-main you wrote: >(3,3) While I don't have the VSAM manuals handy, I think in most cases the share options should be (2,3). Review the manuals Clark Morris > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >Behalf Of Ed Finnell >Sent: Tuesday, May 20, 2014 4:24 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: VSAM question/problem > >What are SHR options? > > >In a message dated 5/20/2014 4:21:17 P.M. Central Daylight Time, >rpomm...@sfgmembers.com writes: > >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. > > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
