On Mon, 7 Jan 2008 20:30:53 -0600, Ed Gould wrote:
>On Jan 7, 2008, at 12:32 PM, Paul Gilmartin wrote:
>> Take my remark as largely rhetorical. IIRC, I was rebutting a prior
>> post expressing a phobic delusion that if PARMLIB had UACC=READ, an
>> incompetently or maliciously crafted job might ABEND leaving an
>> unreleased restrictive ENQ on PARMLIB. I never considered it a
>> realistic concern. ("more likely" means some larger multiple of 0.)
>>
>> Of course, there's always:
>>
>> //STEP1 EXEC PGM=BPXBATCH,PARM='PGM /bin/sleep 9999'
>> //STEP2 EXEC PGM=IEFBR14,COND=(0,LE)
>> //SYSUT99 DD DISP=OLD,DSN=SYS1.PARMLIB
>>
>> ... but RACF won't help you there.
>>
>> Gil:
>
>But the initiator might stop you as RMF has (assuming you are running
>RMF) the disp=shr in its JCL.
And you will be waiting for your exclusive enq on parmlib. Meanwhile, if I'm
not
mistaken, anyone else who tries to enq it will queue behind your exclusive
request.
--
Tom Marchant
----------------------------------------------------------------------
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
