If I understand you correctly, the answer to your question is no.
If an issuing task supplies an ECB with an ATTACH macro the system posts it
complete when the subtask created by the ATTACH completes its processing. This
is usually done so that the attaching task can use a WAIT macro to wait upon
and be notified by the system of the completion of the subtask.
The system does not, however, remove the program object or load module executed
by this subtask from storage, which is an advantage if subtasks that use it are
attached repeatedly. For this reason the attaching task must issue a DETACH
macro for the subtask before it itself terminates.
If instead neither an ECB nor an ETXR parameter is specified in an ATTACH macro
the system does the clean up, removing the executable from storage after it
completes its processing.
Note also that, at least in new code, you should now be using ATTACHX instead
of ATTACH.
John Gilmore Ashland, MA 01721-1817 USA
_________________________________________________________________
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
