Basic ESTAE and subtask question
an ESTAI routine passed once on a single ATTACH could potentially get driven multiple times as an ABEND of the parent task was propagated to various daughter tasks? I'd quibble about an abend being propagated to daughter tasks. I don't think of it as "propagated" (particularly because the specific abend is not propagated). Daughter tasks are abended (13E/33E) because of the (in-process) termination of the parent task (prior to the parent task beginning resmgr processing). But yes, if the parent task has an ESTAI defined, its daughter tasks would have that same ESTAI routine (the control block representing the ESTAE (SCB) is copied so that the subtask has one too). That routine would get control for each task that has it, according to normal recovery rules. If every ATTACH specified ESTAI then the subtasks could end up with a lot of ESTAIs due to this propagation (one for each level in the task tree from the first that used ESTAI). Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Basic ESTAE and subtask question
Well, shoot. I realized as I was quoting it that it was not the latest and greatest, but so little changes in the existing interfaces that I did not worry about it. I tend to work always from the doc for the oldest release of the OS that *we* support, so I don't get seduced by some new feature that is not yet available to me. That is currently V2R1. So -- just curiosity, does not matter to me at this juncture -- an ESTAI routine passed once on a single ATTACH could potentially get driven multiple times as an ABEND of the parent task was propagated to various daughter tasks? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Relson Sent: Friday, July 31, 2020 6:22 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Basic ESTAE and subtask question any recovery routines defined for the originating task are propagated to the new Task" It's a good idea to look at the current level of the books for things like that, since that's where corrections (if any) are likely to show up. I saw Charles' reference in z/OS 2.2 KC but in z/OS 2.4 it has been improved to: "any STAI or ESTAI recovery routines defined for the attached task are automatically propagated to its subtasks." -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Basic ESTAE and subtask question
any recovery routines defined for the originating task are propagated to the new Task" It's a good idea to look at the current level of the books for things like that, since that's where corrections (if any) are likely to show up. I saw Charles' reference in z/OS 2.2 KC but in z/OS 2.4 it has been improved to: "any STAI or ESTAI recovery routines defined for the attached task are automatically propagated to its subtasks." Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Basic ESTAE and subtask question
On Thu, 30 Jul 2020 11:08:36 -0700 Charles Mills wrote: :>I am trying to grasp the implications of "any recovery routines defined for :>the originating task are propagated to the new :>Task" in the ATTACH documentation. (It's under STAI/ESTAI but it's not clear :>to me if it only applies when STAI or ESTAI is in effect.) :>Here's my question: :>A main program issues ESTAEX (exit addr != 0). It then issues an ATTACHX :>with no STAI or ESTAI. While the subtask is still running the user cancels :>the program. Question: will the ESTAEX exit be driven once (only for the :>main task) or twice (for the main task and also as "propagated to the new :>Task")? ESTAE(X) only applies to the task issuing it, not to subtasks. -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Basic ESTAE and subtask question
I am trying to grasp the implications of "any recovery routines defined for the originating task are propagated to the new Task" in the ATTACH documentation. (It's under STAI/ESTAI but it's not clear to me if it only applies when STAI or ESTAI is in effect.) Here's my question: A main program issues ESTAEX (exit addr != 0). It then issues an ATTACHX with no STAI or ESTAI. While the subtask is still running the user cancels the program. Question: will the ESTAEX exit be driven once (only for the main task) or twice (for the main task and also as "propagated to the new Task")? Charles -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
