Preparing for Installation › CADDSPL Linear Data Set (LDS) File Considerations

CADDSPL Linear Data Set (LDS) File Considerations

Up to 32 unique CA Dispatch regions can execute per LPAR. Each region will be linked, using the CA Dispatch SYSGEN, to a unique CADDSPL task. The individual CADDSPL tasks are identified by a unique, user defined, trailing suffix, CADDSPLx. A set of VSAM Linear Data Sets (LDS) used as a data repository to store user report and MSGCLASS data must be allocated for each CADDSPLx task.

A brief understanding of how CA Dispatch and CADDSPL use the LDS files will help you determine the LDS file configuration and size allocations.

• A given CADDSPL task captures and stores user report and MSGCLASS data (that is written to specific user defined JES class and destination combinations) to a set of LDS files. This data can be captured via a pre-JES Spool open intercept or post JES Spool SAPI collector.
• CA Dispatch uses these same LDS files as the input staging areas for the RPI, MSG and ARCHIVE subtasks.
• All bundled reports awaiting printing by the RPO subtasks will also reside within the LDS until released to print on the JES Spool.
• All Online Viewing Report and MSGCLASS report data is stored and retained on the LDS files until the retention expiration is reached.

During a new installation you will allocate and configure one set, or group, of Linear Data Sets (LDS) for use by a specific CADDSPLx task. This set of LDS files consists of one required Root LDS file and a series of one or more appended LDS files. Based on your site's requirements (the need to create separate test and production regions), you may optionally allocate and configure multiple unique sets of LDS files for use by additional CA Dispatch/CADDSPLx regions.

Important! Adjust the MAXCAD value in your SYS1.PARMLIB(IEASYSxx) whenever you are adding a new CADDSPL environment or LDS file. See the following section, Updating the MAXCAD Assignment for more information.