On Mon, 6 Jul 2015 07:22:17 -0400, Steve wrote:

>There is this in the JCL User's Guide:
>
>   A statement requesting exclusive control overrides any number of
>   statements requesting shared control. One of two methods can be used
>   to request exclusive control:
>
>      DISP=NEW, DISP=MOD or DISP=OLD on a JCL DD statement.
>      DISP=NEW, DISP=MOD or DISP=OLD on a dynamic allocation request,
>
>   including dynamic allocation requests that result from the use of
>   certain utility control statements.
> 
I suppose a "utility control statement" may be interpreted to include
the TSO ALLOCATE command.

>So, once you request exclusive control on a dynamic allocation request,
>(including non-obvious uses of dynamic allocation done via
>TSO ALLOCATE or some utility, such as IDCAMS,) you are considered
>to have exclusive control.
>
>I will add that when this exclusive control is obtained for a dynamic
>allocation request, it will not be downgraded again in a later
>step [*** nor when that dynamically allocated DSN is freed?
-- gil ***].
>It will be released when the last step that uses the data
>set completes.
>
Is this an internally generated RCF?

Many years ago, I submitted an SR concerning a sequence of jobs
that left uncatalogued data sets lingering on storage volumes
(sometimes all our storage volumes) when catalog requests failed.
I got WAD (BAD?) because a resolution would have required the
ability to downgrade an ENQ.

I just tested again, and the problem still occurs with TSO messages:

    allocate dsn(TEMP.BAD.NEW) new catalog
IKJ56229I DATA SET user.TEMP.BAD.NEW NOT ALLOCATED, CATALOG ERROR+
IKJ56229I DATA SET NAME CONFLICTS WITH EXISTING DATA SET NAME OR USER IS NOT 
AUTHORIZED TO PERFORM THE OPERATION.
READY

... and job log messages:

18.14.48 JOB08989  IGD17060I DELETE/RENAME FAILED BECAUSE DATA SET IS OPEN  806
   806             ON VOLUME vvvvvv
   806             DATA SET IS user.TEMP.BAD.NEW
18.14.48 JOB08989  IEC614I SCRATCH FAILED - RC 008, DIAGNOSTIC INFORMATION IS 
(040B0425),  807
   807             STEP2,vvvvvv,user.TEMP.BAD.NEW

... (The messages are clearer than I recall from so many years ago.)
Perhaps now that ENQs may now be downgraded, it's time to renew
my SR.

On Fri, 3 Jul 2015 11:07:31 -0500, Scott Fagen wrote:
>>
>>... some stuff ...  Then:
>>FREE DD(DDEXC)
>>    is the ENQ downgraded back to SHR?  Why or why not?
>
>See 
>http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.e0za100/mvssysdsn.htm
> 
That describes JCL behavior; my question concerned dynamic allocation.

Thanks again,
gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to