You have issued a SPLx CLOSE command to shut down the CA Dispatch CADDSPLx environment and after receiving messages similar to the following, the CADZSPLx and CADZSAPx tasks shutdown is delayed or the tasks do not come down at all:
CADD068W SPLx waiting for close of report
CADD184I SPLx Token=0001C4EA Job=ABCDB2 DDname=SYSUDUMP Ord#=00000248
CADD084I SPLx Token=0001C4EA Jid=JOB12345 PrcStep=PROC01 Step=STEP010
CADD085I SPLx Token=0001C4EA Class=X Dest= Origin=Intercept
CADD235W SPLx Job(s) is(are) actively being intercepted by RPI1
Based on this problem description, it sounds like you are using the dynamic INTERCEPT functionality of the CADZSPLx task and this is what is causing the delay shutting down the CADZSPLx and CADZSAPx tasks. You may or may not have seen the following note in the documentation in the CA Dispatch System Programmers Guide where we discuss "Ending CADDSPLx, CADZSPLx Warnings and Considerations"...
Note: It is not recommended that output from very long-running jobs be intercepted, especially jobs that are running for days or weeks.
The output will not be available until the job ends. It is preferable to have the output from the long-running jobs go to the JES Spool and be picked up by the CA Dispatch SAPI Facility.
Clients using the dynamic INTERCEPT functionality of the CADZSPLx have several options available to avoid having this type of problem.
1. Turn off the dynamic intercept functionality altogether and process all data in through the SAPI tasks.
2. Send the output from long running batch jobs or tasks to an output class that is NOT dynamically intercepted, then process the output in through a SAPI task configured to process that non-intercept class. A CA Dispatch RPI task will also need to be configured to process this same class.
3. Issue a 'SPLx CLOSE,IMMEDIATE' command instead of your regular 'SPLx CLOSE' command.