a technique I have used is one control block per task. each cb has an ECB and a head of message chain pointer (que) and two identity strings - one for type of cb and another for identity of owner. It also needs pointer(s) to all other tasks it uses, including main task. main task either has pointer to self or 0. main task also has list of addresses of all cb's for all subtask(s).
for one task to notify another place address of "message" on que w/CD or CDS and then POST ECB of task. Subtasks can remain active until another task tells them to shut down implement in macros. reuse as needed. IBM Mainframe Assembler List <[email protected]> wrote on 11/26/2013 09:57:27 AM: > From: "[email protected]" <[email protected]> > > Then it will probably also need to be passed a flag which can be tested to > > see if it is time to shutdown or continue processing. > > > > The main task can post the shutdown flag at the appropriate time. Once > > shutdown its posted, the subtask winds up its processing, posts the > > completion ECB and exits. > Why not use a WAIT LISt with 2 ECBS being waited on > 1ECB is used to process work > 2ECB is used to QUIESCE or Shutdown ----------------------------------------- The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you
