On 10/02/2013 01:06 PM, Mark Zelden wrote:
> On Wed, 2 Oct 2013 11:47:44 -0500, Kirk Wolf <[email protected]> wrote:
> 
>> Mark,
>>
>> I'm curious - if the PDS is allocated with DISP=SHR, will IDCAMS use ISPF
>> compatible ENQs to serialize the member when deleting?
>>
>> Kirk Wolf
>> Dovetailed Technologies
>> http://dovetail.com
>>
> 
> 
> In a word, no.   But this is a problem all over the OS with various 
> utilities.  If 
> the scenario you want to use IDCAMS w/SHR for deleting a PDS member
> is a concern, then use ISPF services.   If not, then it works just fine and
> does the trick in the overwhelming majority of scenarios that I can think 
> of wanting to use it for.   For example, setting up a batch installation,
> maintenance or production job stream.  If it is something you need to
> repeat on a regular basis, there is probably not a human involved 
> editing the PDS member when you desire to do the delete.   
> 
> Regards,
> 
> Mark
> --
> Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS  
> mailto:[email protected]     
> ITIL v3 Foundation Certified                                     
> Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html 
> Systems Programming expert at http://search390.techtarget.com/ateExperts/

When SHR allocation is used, an enqueue on the member is not as
important as the exclusive enqueue ISPF services uses on "SPFEDIT" Major
name to guarantee no one else tries to open the PDS for output at the
same time with an overlapping directory update, as that would be fatal
for PDS integrity if allowed.  At least for many decades MVS prevents
PDS directory destruction by ABENDing witih 213-30 an attempt to OPEN a
PDS for OUTPUT if it is already OPEN for output elsewhere, but that
means unless a delete process somehow uses the required ISPF SPFEDIT
enqueue, it is subject to "random" ABEND failures if its execution
conflicts with other PDS update activity that also uses SHR allocation
of that PDS.

-- 
Joel C. Ewing,    Bentonville, AR       [email protected] 

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

Reply via email to