At 19:35 -0600 on 04/25/2007, Paul Gilmartin wrote about Re: sysdsn enq:
After all, batch processing FREEs all data sets between steps, but continues to hold the ENQ if a subsequent step uses the same data set name.
Unfortunately due to a poor design in the ENQ support code it can be forced to hold the ENQ longer than should be needed. The situation I am talking about is when step 1 has an exclusive ENQ (DISP=OLD) while step 2 needs only a shared ENQ (DISP=SHR). Since the designers of ENQ didn't bother to support the capability to downgrade the ENQ from EXC to SHR (ie: Keep the ENQ but allocate it to any other task that was waiting for SHR access), step 2 maintains the EXC ENQ even though it only needs SHR access. For some reason, the ENQ code DOES allow a SHR to be altered to EXC if/when no other task has the QNAME/RNAME allocated (although I can not think of a situation where this is of any use).
---------------------------------------------------------------------- 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
