gil,
Thank you and OK. I understand now what you want to do. Complete
generality would be difficult to achieve, but if you can specify the
envelope of all of the MVS utilities you may wish in any circumstances to
attach, then a simple Rube Goldberg solution to your problem is possible.
First, you attach a driver subtask
The driver subtask then attaches one or more subsubtasks, one for each
previously envisaged utility you wish to use on some occasion AND posts the
ECBs associated with the utilities you do not wish to use on that occasion
complete.
The driver subtask then WAITs on an ECBLIST, the last element of which must
have its high-order bit set, ccintaining an ECB for all envidaged utility
invocations. (See the discussion of the WAIT macro parameter ECBLIST= in
SA22-7607-03, z/OS MVS Programming: Assembler Services Reference, Volume 2
(IARR2V-XCTLX).)
Then as each subsubtask finishes its work, it POSTs its own associated ECB
complete.
Your driver subtask is then dispatched again after ALLl of the ECBs for the
subsubtasls you have in fact attached hasve been posted complete.
You could do something fancier by constructing an ECBLIST for only those
utilities you wish to invoke on a particular occasion dynamically, but using
the extra posted-complete ECBs is probably a better choice unless you write
a lot of HLASM code of this sort.
This nonce terminology is barbarous., but I hope it is also unambiguous.
John Gilmore
SystemCraft LLC
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@no-spam with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html