In reading the doc on DSENQSHR (in JCL, JES, GRS, etc.), I am wondering what the down side might be.
If one is using a Production Control system of some kind, what pitfalls do you envision by allowing an ENQ to be demoted to non-exclusive (SHR)? I can see problems for restart if a file gets mangled during reorg, or delete/define/load that is detected by the next step which uses DISP=SHR as an example. Granted, that JOB should RUN with DSENQSHR=DISALLOW. Regards, Steve Thompson Humana, Inc. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
