Auto-starting the CADZSAPx (SAPI) and CA Dispatch related subtasks.
Article ID: 23161
Updated On:
Products
Issue/Introduction
When we start the CADZSPLx task, it automatically starts the CADZSAPx SAPI task. When we start CA Dispatch, it automatically starts it's own RPI,MSG,RPO,ARCH and EXTR tasks. What causes this to happen? Is there a particular startup/shutdown sequence that should be followed?
Environment
Component: Dispatch
z/OS
Resolution
Regarding startup of the CADZSPLx task itself, the only start command that would ever be issued from the console is the /S CADDSPLx command (where the 'x' is the unique suffix for the CADZSPL environment). The /S CADDSPLx command submits the environments initialization routine that when successful, will dynamically start the CADZSPLx task. This command can be added to, and issued from your sites automation package.
The CADZSPLx task should be started BEFORE CA Dispatch and it's various subtasks are started.
When shutting things down, shut down Dispatch first using the STOPCADS or 99STOPCADS command. This will automatically end any active CA Dispatch subtask (RPI,MSG,RPO,ARCH and EXTR). Then, use the appropriate /F SPLx,CLOSE command to bring down the CADZSPLx address space. When CADZSPLx comes down, it will also end the CADZSAPx SAPI task.
Regarding auto-startup of the CADZSAPx SAPI task...
The CADZSAPx started task that you see out on your system appears whenever one of the individual SAPI tasks (SAPIRPI1, SAPIRPI2, SAPIMSG or SAPIARCH) are started. At no time is a start command ever issued specifically for the actual CADZSAPx STC that you see.
When you run DDEXLDSI to configure the CADDSPLx environment, you use ADD statements to define the processing criteria. These ADD statements not only define the RPI, MSG and ARCH class processing criteria, they also define the SAPI task processing criteria. These ADD statements include an "INITIAL" parameter that dictates the initial status setting for each SAPI task at the start of CADZSPLx. The DEFAULT "initial" parameter setting is DYNAMIC so it is what most clients would likely be using. This DYNAMIC setting means that the SAPI tasks are reinitialized with the same status that they had at the previous CLOSE point.
For example, the SAPI tasks that were active when the SPLx,CLOSE command was issued will automatically be restarted when the CADZSPLx comes back up. The ones that might have been inactive will remain inactive upon startup of the CADZSPLx task.
Regarding auto-startup of the CA Dispatch subtasks (RPI,MSG,RPO,ARCH,EXTR)...
If you want to control startup of the CA Dispatch related subtasks, then you should code the appropriate commands in the DSSTARnn member that is referenced via the 'START=' symbolic in the CADSDISP/DSEXDISP JCL. This is the member in the CADSOPTN library that dictates which CA Dispatch subtasks will automatically be started when "DISPATCH" is started.
Additional Information
The CA Dispatch documentation is available for download from our legacy bookshelf located HERE
For additional information on what parameters are available for configuring the CADDSPLx environments processing criteria and auto-start options, please see Chapter 7 entitled "CADDSPL Operation" in the CA Dispatch System Programmers Guide.
For additional information on what commands are available for coding in the DSSTARnn member used for auto-starting the CA Dispatch subtasks, please see the section entitled "Starting And Ending Tasks" located in the Appendix A: Operator's Handbook chapter in the CA Dispatch Reference Guide.
You might also be interested in reviewing the following Knowledge document as well:
Article Id: 32927 - Alternative methods for starting and ending the Dispatch subtasks instead of using the VOPMI100 screen.
Feedback
