In a recent note, Walt Farrell said: > Date: Wed, 25 Apr 2007 20:28:23 -0400 > > > Hello: Is there a way to prevent the SYSDSN ENQ from being removed when you > > dynamically de-allocate a data set? > > Out of curiosity, why would you want to do that? What purpose does it > serve to hold the ENQ when you no longer have the data set allocated? > I can envision a reason: perhaps to prevent another job's grabbing the data set between the FREE and another ALLOCATE (perhaps to a different DDNAME). 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. I consider it to have good purpose to do this.
That said, and positing the reason stated, if the OP were to perform the second ALLOCATE _before_ the first FREE, the ENQ would be held; or he could perform an otherwise meaningless ALLOCATE (no DDNAME required) early and FREE it late to achieve the same effect. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
