On Fri, 29 Sep 2006 08:12:49 -0600, Paul Gilmartin <[EMAIL PROTECTED]> wrote:
>In a recent note, Bruce Black said: > >> Date: Wed, 27 Sep 2006 14:52:14 -0400 >> > >> > Isn't the ENQ done at job intiation time and the LOCATE at step >> > initiation time? >> Yes, but the name returned by LOCATE will be ENQed at step initiation if >> different from the name ENQed at job init (e.g. a GDG absolute >> generation or an alias) >> >... leading to possible job failure (ABEND? JCL ERROR?) if the >returned name has a conflicting ENQ. I believe it will not wait in >this case. > Already covered. It used to always fail. I know in (at least) MVS/XA you could zap the allocation table (IEFAB445) to turn on the DEFSDSWT flag so the job would wait instead of failling. That same behavior has been controlled via SDSN_WAIT WAITALLOC(YES) in the ALLOCxx parmlib member since MVS/ESA. Regards, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group mailto: [EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
