Starting Your Product › How to Configure Without CA MSM › Test and Validate Operation › Test and Validate CADDSPL

Test and Validate CADDSPL

To test CADDSPL, follow these steps :

1. Issue the F SPLx,STAT X modify command from the console.

   This command will show utilization statistics for your CADDSPL linear data sets. Make note of the number of blocks in use and the "captive" count.

2. If the CADDSPL tasks are down, issue the F SPLx,S RPI1 modify command from the console.

   This command will start the Intercept and the SAPI task for the RPI1 task.

3. To test the CADDSPL open intercept, execute a test job that will produce a test report to be intercepted by CADDSPL.

   You can use the following JCL to do this:

   //STEP1 EXEC PGM=IEBGENER
   //SYSUT1   DD *
     Test Report for CADDSPL Spool and CA Dispatch testing
   //SYSUT2   DD SYSOUT=(A,rptname),DEST=DST1
   //SYSPRINT DD DUMMY
   //SYSIN    DD DUMMY
   

   where:

   A is equal to a CADDSPL RPI1 selection class defined in the prior Allocate LDS Files and Configure CADDSPL Processing Options step.

   DST1 is equal to a CADDSPL RPI1 selection destination defined in the prior Allocate LDS Files and Configure CADDSPL Processing Options step.

   Note: Destination is optional.

4. Issue the F SPLx,STAT X command again and make note of the Blocks in Use and "Captive" count. If both counts are higher than the amount shown in Step 1, your CADDSPL spool intercept function is working properly.
5. To test the CADDSPL SAPI interface, execute the IEBGENER job (as in Step 3) again. However, this time, change the class/destination so that they are not CADDSPL RPI1 selection class/destination values. (This should allow the test report to go out to the JES queue.)
6. Change the class/destination of the test report in the JES queue to the class/destination you have defined in one of your CADDSPL RPI1 selections; this should cause the SAPI task to move the test report from the JES queue into CADDSPL.