On Fri, 15 May 2020 13:50:08 -0700, Charles Mills wrote:
>Thanks. Yeah, I love BPXWDYN but ALLOC/FREE would be easier here.
>
How? I prefer BPXWDYN because of the finer control of error reporting.
And I use RTDDN() lest the Exec be embedded in a larger process with
the risk of DDNAME collision, perhaps because of concurrency.
>I see that
>ALLOC supports SPIN(UNALLOC) but you are saying I don't need it?
>
From the JCL Ref.:
UNALLOC
JES2 only. Indicates that the system makes the data set available for
processing immediately when the data set is unallocated. If you
dynamically unallocate the sysout data set, either explicitly or by
specifying
FREE=CLOSE, the system makes the data set available for processing
immediately. If you do not dynamically unallocate it, the sysout data set
is unallocated at the end of the step, and the system makes it available
for processing then.
So, you need SPIN to process before end of step.
And for JES3, you're SOL. The only supported option is NO.
(Unless you spawn your script with _BPX_SHAREAS=NO? Ugh!)
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
