On 2 Aug 2006 18:46:04 -0700, in bit.listserv.ibm-main you wrote: >At 12:22 -0400 on 08/01/2006, Wayne Driscoll wrote about Re: Data set >ENQueues and DEQueues in Jobs: > >>I could see how a downgrade would be useful. For instance: I have a >>resource shared. Now I need to update the resource, so I perform an >>S->E. Now, I want to allow others to see the update, but I don't want >>to allow an exclusive user to lock me out of the resource, so a E->S >>change would allow this to happen. > >Even more importantly, as I've noted in prior messages in this >thread, the capability to do a E->S downgrade would fix the current >"Design Flaw" in the Initiator where if you follow a Job Step that >has DISP=OLD/MOD for a Dataset with DISP=SHR Job Steps, these >subsequent Job Steps keep the exclusive ENQ until the Job is over (or >there are no more steps using the dataset). Support for E->S >downgrade would allow other jobs to take off once the last >DISP=OLD/MOD step is done and the first DISP=SHR step starts.
I was under the impression that the initiator was able to downgrade from NEW/OLD/MOD to SHR between steps. ---------------------------------------------------------------------- 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
