> finer control of error reporting ... And I use RTDDN() lest the Exec be > embedded
I hear you. This is a one-off internal-use-only. Something of a proof of concept. If this ever became a "product" I would probably re-write in C++ and worry about that sort of thing. > So, you need SPIN to process before end of step. I would think so but @Rob Jackson seems to indicate not. Easy to add if so. > And for JES3, you're SOL. The only supported option is NO. Again, this is a one-off internal-use-only. JES2. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Friday, May 15, 2020 2:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Looking for clarification/guidance on SMTP DD FREE/SPIN 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!) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
