What is CA/Broadcom's recommendation for running the CA Dispatch ARCHIVE and EXTRACT subtasks.
Should we run them INTERNALLY under the main CA Dispatch address space? Or, is it better to run them EXTERNALLY in their own address space?
z/OS, Dispatch, archive, extract,11.6,11.7,internal,external,subtask
If you run these subtasks INTERNALLY, It basically means that CA Dispatch is "single threaded" in that, it can only be bouncing I/O to one subtask at a time. For example, if archive or extract is running internally and a tape mount request comes up, all other activity in CA Dispatch STOPS until that tape mount is satisfied. So, users and report processing functions could be affected.
When you run the EXTERNALLY, these subtasks run in their own address spaces and consequently, create very little overhead on the MAIN Dispatch region. User and report processing functions are not affected in the same manner as they would be if running these subtasks internally.
It is for the above reasons that CA recommends that archive and extract run EXTERNALLY.
The CA Dispatch documentation is available for download from our legacy bookshelf located HERE
There is a very comprehensive discussion regarding the archive and extract subtasks, running them as internal or external, startup and shutdown commands, as well as CA's recommendation to run them externally in Chapter 2 of the CA Dispatch User Guide For the Report Administrators Manual. In here, you will find a section entitled STARTING AND ENDING THE SUBTASKS. Read through this entire section and you will get to a subsection entitled RUNNING SUBTASKS INTERNAL OR EXTERNAL. The answers to many of your questions can be found here.
For information on specifically setting the ARCHIVE and EXTRACT tasks up to run as STC's see the HOW TO START EXTERNAL TASKS AS STARTED TASKS topic in the CA Dispatch Reference Guide towards the back, in the A: OPERATORS HANDBOOK section.