>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 don't thinks that's accurate. DSN allocation is not cleared until EOJ. Hence the scramble with GDG's in a job, especially if you create more than one in the same one. The same thing can be proven with allocation for step N. Allocate a DSN under TSO and then submit a job. Even if a job will not touch the file for hours, the job will hang in ENQ. It's even 'worse' in a JES3 environment. The only way around it is dynamic allocations; then you have synchronisation issues. All OS's have enq-like structures, or they have data integrity issues. Don't try to outsmart them; you'll outsmart yourself! - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
