Hmmm. That would have been a much simpler approach, although I am a little reluctant to touch my dub setting because that code is early in the process and has been working for years. If I screw it up, gosh knows what stops working.
This new code -- it only runs if the user cancels the job. There's a limit to how badly you can screw up a job that the user has already cancelled! <g> Ah, looking at my code DUBPROCESS (1) is what I *am* setting, when I do a set_dub_default(), which is not always. Not sure if I am doing one in my ABEND test situation or not. I think not. Thanks. I will keep this in mind. If this turns out to be problematic then DUBPROCESS would be an alternative approach. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Gord Tomlin Sent: Thursday, July 30, 2020 4:31 PM To: [email protected] Subject: Re: ESTAEX exit WAIT question <snip> Taking these two posts together, I think you should look at BPX1SDD/BPX4SDD a.k.a. set_dub_default(). If you set the value to DUBPROCESS in the job step, before ATTACHing your subtask, the subtask will be a separate process and should clean up at its termination. The default, DUBTHREAD, does not cause the subtask to be a separate process, and in that case I would expect that the cleanup will not occur until the parent (job step) task ends. https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.bpxb100/sdd.htm ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
