We had a similar intermittent problem a while back. A multi-step DB2 backup job would occasionally get a data set conflict and fail. We put into automation (Netview SA) a response to the conflict message that would display any enqueue on the resource: D GRS,RES=(*,dsn). We never found a culprit. The GRS command never showed any other enqueue. We finally decided that it must be some kind of timing glitch within the job itself, that it was tripping on its own shoelaces. We restructured the job (don't know the details), and the problem went away.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile jo.skip.robin...@att.net > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Charles Mills > Sent: Monday, February 15, 2016 11:00 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: [Bulk] Re: Issues with VSAM Enqueuers and Batch job with IDCAMS > > I think Lizette said the problem is fleeting. By the time you know you have the > problem ... it's gone. > > Charles > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Pinnacle > Sent: Monday, February 15, 2016 10:50 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Issues with VSAM Enqueuers and Batch job with IDCAMS > > > Lizette, > > Run the GRS Monitor, you'll get your answer. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
