> What options are those?
"For applications that dynamically allocate a spin SYSOUT data set
(unallocation at Close - Key X'001C')
but fail to issue FREE=CLOSE or SPIN=UNALLOC, JES2 does not free spool tracks
allocated to the spin
data set until the job is purged. In this case, end-of-task processing
deallocates the data set and job
purge processing returns the allocated tracks."
That text is confusing, since FREE and SPIN are keywords on the DD statement
and X'001C' is DALFREE, but DALSPIN (X'8013') would seem to be what is relevant
for the allocation. There is a DUNSPIN ('X'8013') on unallocation that is
documented as having the same effect, but if the data set doesn't already have
an independent track group then unallocate can't change that. I've sent an RCF.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Charles Mills [charl...@mcn.org]
Sent: Sunday, May 17, 2020 11:19 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Looking for clarification/guidance on SMTP DD FREE/SPIN
> Haven't you switched to CSSMTP? What's the drop dead date on SMTP?
Nope and I don't know. I Googled <z/os smtp lifecycle> and <z/os smtp eos>
and got no hits. Do you know?
> Do you want the SPOOL space release after the e-mail goes out? If you do
dynamic allocation then you need to use the right options.
Thank you. Yes. What options are those?
> Why put it in your JCL at all.
That sort of knowledge was indeed one of the purposes of my query.
Charles
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
