Rather than rely on task structure to limit failure damage, each task should establish its own recovery environment and pass back a return code via some non-destructive way.
Recovery processing is also covered in the Assembly Services Guide and the Authorized Assembly Services Guide. Scott, you are getting off into the fun stuff that will cause you to tear your hair out while developing and debugging it, but once you get it running right it is very gratifying. Chris Blaicher Principal Software Engineer, Software Development Syncsort Incorporated 50 Tice Boulevard, Woodcliff Lake, NJ 07677 P: 201-930-8260 | M: 512-627-3803 E: [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Gilmore Sent: Wednesday, August 28, 2013 8:16 AM To: [email protected] Subject: Re: Task to subtask communications I recommend that you use the PAUSE/RELEASE pair instead of WAIT/POST. The WAIT/POST pair is, like GETMAIN/FREEMAIN, lumbered with the detritus of the ages, much of it ugly. Let me also add that another important, in some contexts crucial, use of subtasks stems from the fact that failures within them are less catastrophic. Suppose that task A attaches subtask B and that subtask B in turn attaches its own subtask C. Now if C fails/ABENDs, A and B survive; and if B fails A survives [B and its subtask(s), C here, are terminated]. The idea of relegating perilous undertakings, those that may fail, to subtasks that do not bring down the whole shebang when they do in fact fail is thus a very useful one. (This same recoverability argument can sometimes make the use of multiple address spaces highly desirable, but I am not sure you are quite ready for that.) John Gilmore, Ashland, MA 01721 - USA ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ATTENTION: ----- The information contained in this message (including any files transmitted with this message) may contain proprietary, trade secret or other confidential and/or legally privileged information. Any pricing information contained in this message or in any files transmitted with this message is always confidential and cannot be shared with any third parties without prior written approval from Syncsort. This message is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any use, disclosure, copying or distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Syncsort and destroy all copies of this message in your possession, custody or control. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
