Starting Your Product › How to Configure Without CA MSM › Step 1. Allocate LDS Files and Configure CADDSPL Processing Options › The CADDUTIL Utility

The CADDUTIL Utility

The second step of job DDEXLDSI executes program CADDUTIL. Control statements for CADDUTIL define all of the processing options needed to to run both the CADDSPL and post-JES Spool report collector SAPI tasks.

CADDUTIL stores these options into the Root LDS.

Note: For more information about the processing options and the CADDUTIL utility, see the CADDSPL Operation chapter in the CA Dispatch Systems Programmer Guide.

Modify the default settings where necessary so that the values specified are compatible with your site requirements. Be sure to consider the following critical ROOT, ADD and APD configuration statements:

• ROOT Statement specifies the MAXDS value.

  The MAXDS value must equal the maximum number of reports and MSGCLASS entries that can be stored within the LDS. The following shows the format of the ROOT initialization statement:

  ROOT     DDname = ddname
  

  [ {, INIT / ALTER } ]
  [, Div = ( nnnnn [ , nnnnnn ] [, {CHECKing/NOCHECKing} ]) ]
  [, Index = nnnnnnnnn ] 
  [, Lock = ( nbr ] [, time ] ) ]
  [, MAXDs = nnnnn ]
  [, MDWarn = nnn ]
  [, Order = ( field1 [, field2 [, … ] ] ) ]
  [, PFcount = nnnnnn ]
  [, PRintline = nnn ]
  [, PUrge = ( [ Asynchro/Synchro ]  [, {  Clean/Quick } ] )    
  [, SCan = ( [ SEQuential/SORTed ]
  [, UPdatbitm =   [ ON/OFF ]
  [, Util = ( [ utl1 ] [, utl2 ] ) ]
  [, WPurge = nnnn ]
  [, ENCrypt = ([OFF / ICSF ] [ , nnn ]}  ]
  

   	[, PAGEOut = ( nnnnn  [, {INTERLeav/SEQUENtia} ]) ]
  

  The default setting for MAXDS in the DDEXLDSI JCL is 123568. This setting is a model only. It requires modification to your site specification.

  Important! Consider carefully when calculating the MAXDS value. The MAXDS value cannot be dynamically changed after the Root LDS has been allocated and configured. To change the MAXDS value, you will have to do an OLV unload, reallocation / reconfiguration of the LDS files, and an OLV reload.

  Note: For more information about MAXDS sizing calculations, see the "System Requirements" chapter.

• ADD Statement specifies the task identifier, associated input class / destination combination and action values. The following shows the format of the ADD initialization statement:

  Add task

  [, Class = class ]
  [, Dest = destination ]
  [, Action = action ]
  

  		[, Initial = [Dynamic/Start/STop] ]
  

  The following shows sample ADD initialization statements with task, associated Class / Destination combinations and action variables. By default, the DDEXLDSI job is set up to process user report data as follows:

  • All user report data written to Class A / Destination RPI1 will be captured and assigned to task RPI1.
  • All user report data written to Class A / Destination RPI2 will be captured and assigned to task RPI2.
  • All user report data written to Class A / Destination RPI3 will be captured and assigned to task RPI3.
  • All user MSGCLASS data written to Class S will be captured and assigned to task MSG.
  • All user report data written to Class X will be captured and assigned to task ARCH.

  All tasks, except MSG, will dynamically intercept report data. These settings are examples and are site specific. They will require modification.

  ADD RPI1 , C = A , D = RPI1 , A = INTERCEPT

  ADD RPI2 , C = A , D = RPI2 , A = INTERCEPT

  ADD RPI3 , C = A , D = RPI3 , A = INTERCEPT

  ADD MSG , C = S

  ADD ARCH, C = X , A = INTERCEPT

  Important! CADDSPL will capture (pre-JES Spool via open intercept and post JES Spool via SAPI data collector) and store all reports and MSGCLASS (all MSGCLASS data will be processed via SAPI data collector) output written to these class/destination combinations.

  In a later step in the installation process, you will enter these same class and destination combinations on the VSGMU105 Dedicated Sysout Control Information Screen. If these class or class/destination combination values do not match the corresponding values defined to VSGMU105 Dedicated Sysout Control Information Screen, the reports and MSGCLASS stored in the LDS cannot be processed by the RPI, MSG or ARCH subtasks in CA Dispatch.

  Note: For more information on class and destination combination settings, see the Distribution Considerations section in the "Installation Options" chapter of the CA Dispatch Systems Programmer Guide. Also see screen VSGMU105 Dedicated Sysout Control Information in the "Sysgen Screens" chapter in the CA Dispatch Reference Guide.

• APPEND statement specifies associated JCL DDNAMEs.

  The following shows the format of the Append initialization statement. An APPEND statement must be added for each appended LDS file defined to CADDSPL. The CADDUTIL utility will initialize each corresponding LDS file referenced by DDNAME.

  Append/Apd DDname = ddname     {, INIT / DELETE }
  

  The following shows the sample Append initialization statement with the critical variables. By default, the DDEXLDSI job is set up to initialize and append two LDS files using the DDNAME of APD1 and APD2.

      APD   DDNAME = APD1 , INIT
  

      APD   DDNAME = APD2 , INIT
  

  This sample shows DDEXLDSI JCL with the associated DDNAME. << accurate?? >>

      //UTIL    EXEC PGM=CADDUTIL,REGION=6M
      //STEPLIB  DD  DISP=SHR,DSN=CAI.CADSLOAD         <==
      //ROOT     DD  DISP=SHR,DSN=CAI.CADDLDS.ROOT     <==
      //APD1     DD  DISP=SHR,DSN=CAI.CADDLDS.APPEND01 <==
      //APD2     DD  DISP=SHR,DSN=CAI.CADDLDS.APPEND02 <==
      //SYSPRINT DD  SYSOUT=*
      //SYSIN    DD  *
  

  Note: In a later step in the installation process, you will have to enter both the CADDSPLx Task Suffix and the name of the Root LDS file created by this step on the Sysgen Control Information Screen (VSGMU110). This will assign or link the specific CA Dispatch task to an associated CADDSPLx task. For more information, see the Test and Validate Operation step.