How to turn the dynamic INTERCEPT function of CADZSPL off
search cancel

How to turn the dynamic INTERCEPT function of CADZSPL off


Article ID: 229940


Updated On:


Dispatch Output Mgmt


Provide steps for how to turn off the INTERCEPT function of the CADZSPLx task.  Also, is an IPL required for the change to take affect?


Release : 11.7

Component : Dispatch


The INTERCEPT function of the CADZSPLx task can be turned off in either of 2 ways. An IPL is NOT required to affect the change.


1. The INTERCEPT function can be turned off by entering the following operator command against the appropriate CADZSPLx task:



2. The INTERCEPT function can also be turned off from the Dispatch VOPMI100 screen by tabbing down next to any task that shows a STATUS of 'ON' and typing an 'I' in the Opt column next to that task.

* It doesn't matter if the task is showing ACTIVE or NOT ACTIVE

* After typing the 'I' and pressing enter, the STATUS will change to "OFF". There may be a delay in the STATUS change depending on whether or not there is an active intercept currently in progress.


- Turning the INTERCEPT function OFF is a "real-time" and permanent change. It will remain OFF even through IPL's and recycles of the CADZSPLx tasks.

* The intercept function CAN be turned back on again if the appropriate command is issued or if someone types an 'I' next to the task on the CA Dispatch VOPMI100 screen.


- The INTERCEPT function can be permanently disabled by deleting and re-adding the appropriate task using the 'A=NOI' parameter setting on the ADD statement for that task. For more information on how to accomplish this see Knowledge Article Id: 44259 Title: How can I be sure that Intercepts do not get started by accident?

Additional Information

The following additional information and examples come from the CA Dispatch documentation:


This command stops one or all intercepts, SAPI tasks, or both. The letter P can be used in place of STOP.

The intent of the STOP command is to end intercept(s) and/or SAPI task(s) safely. To ensure this, the STOP command, by default, will process in the following way:

- All reports must be closed, unallocated and ready to be processed by CA Dispatch before the Intercept and/or the SAPI task stops. Therefore, when the intercept or SAPI task is processing a long report, such as output from CICS, IMS, or DB2 is, the stop process can take a long time to finish.

Following are examples of the STOP command:

- F SPLx,P RPI1 stops both Intercept and SAPI tasks related to RPI1, waiting for long-running reports to end.
- F SPLx,P RPI2,S,I stops the SAPI task related to RPI2 criteria immediately
- F SPLx,P ALL,IN stops ALL currently running intercepts