On Fri, 11 Jul 2014 00:32:02 -0400, Robert A. Rosenberg wrote: >At 15:14 -0500 on 07/10/2014, Tom Marchant wrote about Re: SMP/E >APPLY CHECK failing: > >>Most likely you have DISP=OLD on SCEELKED. It should be SHR. > >True. OTOH, this is also fall-out from the allocation ENQs being >broken for years. The RNAME being used is DSN NOT DSN+VOLSER like >ISPF does. There is NO valid reason to issue an exclusive ENQ on a >dataset name without qualifying it by what volume it lives on. Just >because I want exclusive access to X.DSN on VOLSER1 does not require >that access to a X.DSN on VOLSER2 be denied. As I said ISPF has >solved this issue for EDITs by having its own QNAME and having the >RNAME include the VOLSER that the dataset you are editing resides on. >This has been a design flaw that has existed ever since Shared DASD >and SYSTEMS ENQs have been supported and IBM has done nothing to fix >the problem by revamping the ENQs done by allocation. > Unfortunately:
o There are too many cases, such as job initiation, where the ENQ EXC is obtained before VOLSER or MEMBER can be known. o There are so many facilities written by both IBM and customers which trust ENQ EXC SYSDSN, sometimes issued by the other party, to preserve system integrity, that any change would require an enormous resource for refactoring, and be extremely dangerous. But, I believe that's all irrelevant, and the problem reported by the OP: On Thu, 10 Jul 2014 13:21:32 -0400, Rob JACKSON wrote: >Anyone have any ideas for a quick fix for this type of situation? >GIM54701E ** ALLOCATION FAILED FOR SMP00027 - IKJ56246I DATA SET CEE.SCEELKED >NOT ALLOCATED, FILE IN USE. > ... ... has nothing to do with any ENQ. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
