Picking up on something Paul G. said in another thread, I realized I have never known *why* the system issues JOB scope ENQ's on DSN's.
I do realize that it is most probably to avoid an ENQ "deadly embrace" somewhere along the line, but for the life of me (well, and maybe because it's Friday) I can't think why a DSN ENQ would be JOB scope instead of STEP scope. At least not by default, anyway. I suppose if you create a dataset in step A and then use it DISP=SHR in step B (or F or Z, way down the line), if it were not JOB scope ENQueued some other job could come in-between your create and use steps and delete it on you, or update it in some clever but unscrupulous way, but I really can't think of a scenario that means JOB scope ENQ's are required. TIA for curing my ignorance on this subject. Peter -- As of 04/01/2007 I have a new email address, so please update your address book: Peter (dot) Farley (at) broadridge (dot) com This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- 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
