Claude, TOL(ENQF) should be a hint. This is telling DFSMSdss that if it can't get exclusive ownership it's OK - just go ahead and dump the dataset anyways no matter why or how it is being updated.
Anything that isn't allocated already will get an exclusive enqueue unless you specify the SHARE option. If you require exclusive enqueue, and you don't want those fuzzy copies you get from TOL(ENQF) to be too unusable, then I suggest you use CONCURRENT COPY (CC) so the enqueue is released as soon as CC has it's sessions set up. Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Claude Richbourg > Sent: Friday, 3 February 2006 12:18 AM > To: [email protected] > Subject: ADRDSSU enqueue question. > > Good morning all, > > It's a slow day and I have a question on how ADRDSSU behaves during a > logical backup. This may be a silly question, but I am curious. > > We had a short running batch job fail last night with a JCL error, > while another long batch job was running doing a logical backup that > included the needed proclib dataset referenced by the short running > batch job. > > Environment is z/OS 1.4. > > This one long running ADRDSSU - logical batch job, (runs one hour most > times), had to be backing up the library that the short running batch > job needed. Timing issue I realize. The short batch job had a proclib > statement and an include statement. The short running batch job had a > JCL error and here is the messages from that job and JCL: > > > From the short batch job JCL: > PROCLIB JCLLIB ORDER=xxx.xxxx.xxxx.xxxx.PROCLIB > INCLUDE MEMBER=xxxxx > > Output from short batch job: > IEFC003I ALLOCATION ERROR IN PROCESSING A JCLLIB STATEMENT > > IKJ56225I DATA SET xxx.xxxx.xxxxx.xxxx.PROCLIB ALREADY IN USE, TRY > LATER+ > IKJ56225I DATA SET IS ALLOCATED TO ANOTHER JOB OR USER > > IEFC017I INCLUDE xxxxx WAS NOT FOUND > > > I looked up the IEFC003I message and it is somewhat clear. > I know that we can re-run the short batch job and it finishes okay now, > but, my question is: What kind of an enqueue does ADRDSSU put on the > datasets during a logical backup. It seems like it must be a DISP=OLD, > but can I code anything different to help the short running batch job in > the future, since all it does is READ the proclib include member? The > schedule is kinda tight during nightly batch processing and since the > short batch job kicks off based on a predessor job, which is at > different times during the nightly batch cycle. > I haven't found anything from an ADRDSSU perspective. We dump with > TOL(ENQF), but that is for ADRDSSU. > > Just curious what ADRDSSU does during a logical and can we sneak past > this scenario in the future somehow? > > Thanks all, > Claude > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
