My following suggestions may be missing the desired goal. But, what the heck
here they are:
1. Use IEFBR14 with the required dsn and disp=old in step1 and in the last
stepx after all required steps
2. Use IEHPROGM to rename the dsn(member)
3. Use IDCAMS alter dsn(member)
4. Use RACF batch step1 to change access to none and then access to job userid
and then last step to reset to normal access.
David Mingee
Mainframe Consulting
9206 Aintree Drive
Indianapolis, IN 46250
From: Steff Gladstone <[email protected]>
To: [email protected]
Sent: Tuesday, April 21, 2015 4:00 AM
Subject: Re: ENQ for the life of the job
Thank you all for for help. The obvious question that remains is: how
does the operating systen itself maintain a continuous ENQ over several job
steps for a dataset allocated in the first step with disp=(mod,pass)? Is
there a special privileged ENQ operation that only the operating system has
access to?
On Mon, Apr 20, 2015 at 10:26 PM, Tom Brennan <[email protected]>
wrote:
> Jousma, David wrote:
>
> ... I'd use standard JCL DISP=OLD processing on a dummy dataset name that
>> includes the program name as part of it.
>>
>
> Maybe someone mentioned this already, but I was thinking even simpler -
> use the same job name each time if the user has no control over the JCL,
> with JES2 DUPL_JOB=DELAY which I think might be the default.
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
