Starting Your Product › How to Configure Without CA MSM › Test and Validate Operation › Test and Validate the CA Dispatch Main Region

Test and Validate the CA Dispatch Main Region

Perform the following steps to initially configure and test the CA Dispatch main region:

At this point, you can sign on to the system through VTAM, or if you installed the TSO or CICS interfaces, follow the SIGNON instructions in the Reference Guide.

Your first task should be to access the Sysgen screens (Option 9 on the Report Distribution Option Menu) to set up basic defaults and complete the initialization tasks.

1. Sign onto CA Dispatch and select Option 9 Sysgen from the CA Dispatch main menu.
2. Select Option 0 from the Sysgen Option Menu. Enter the necessary SYSOUT Class/Destination information on the Dedicated Sysout Control Information Screen (VSGMU105).

   Important! This screen is used to assign or link the CA Dispatch task to an associated CADDSPLx task.

   The Sysout Class and Destination combination values for the RPI1, RPI2, RPI3, MSG and ARCH tasks entered here must correspond to the Sysout Class and Destination values defined in Step 10. Allocate and Initialize CADDSPL LDS.

   Note: The multiple Archive tasks all process input from one ARCH Class/Destination combination defined in CADDSPL.

   After making your updates, PF3 to save your changes.

3. Select Option 1 from the Sysgen Option Menu. Enter the necessary control parameters on the Sysgen Control Information Screen (VSGMU110).

   Important! This screen is used to assign or link the CA Dispatch task to an associated CADDSPLx task.

   Enter the appropriate value into the Task Suffix field, where x identifies the CADDSPLx task. For example, if your CADDSPLx task is named CADDSPLP, you would enter P into the Task Suffix field. The CADDSPLx task names were defined in the Tailor the Execution JCL step.

   Enter the actual Root LDS Dataset name that was allocated in Step 10. Allocate and Initialize CADDSPL LDS.

   Some of the new and important fields required on this screen are Undefined Report Definition, Manifest Position, Bundle Sort Order, Bundle Recovery DSN Prefix and Unit.

   After making your updates, PF3 to save your changes.

4. Select Option 9 from the Sysgen Option Menu. Enter the control parameters necessary for online viewing on the Online Viewing Control Information Screen (VSGMU190). After making your updates, press PF3 to save your changes.
5. Select Option A from the Sysgen Option Menu. Enter the default archive parameters on the Archive Control Information Screen (VSGMU210).

   To avoid contention with duplicate file names when using multiple archive tasks, we suggest that unique qualifiers (such as ARCH1, ARCH2, ARCH3) be added to the DSN prefix defined on the Sysgen Archive Task Information Screen (VSGMU215).

   After making your updates, press PF3 to save your changes.

   Note: DSSTAR00 in the START JCL PROC override statement will not autostart any CA Dispatch tasks to allow for Sysgen tailoring. Changing this member to DSSTAR11 will autostart the distribution, status, archive, and extract tasks. DSSTAR12 will autostart distribution and status only.

   Note: If CADDSPL has not intercepted any reports yet, RPI and ARCH will fail with an "LDS empty" message. Restart RPI and ARCH after a report has been captured and stored in the LDS.

6. After you complete the sysgen by viewing and modifying the CA Dispatch online screens, you can manually start and test functions by using the following commands at the Enter Next Task Code prompt:

   S DIST—Starts the distribution tasks that bundle reports (RPI, RPO, MSG)

   S ARCH—Starts the archive task, which archives reports to tape

   S EXTR—Starts the extract task, which reprints reports from tape

   S STAT—Starts the status task, which records external ENF Event status to the database

If you had problems bringing the system up, make the required corrective modifications and resubmit the job. If you cannot resolve the problem access http://ca.com/support, the CA web site to quickly locate answers to many questions. Technical support is available 24 hours a day, 7 days a week.