ZAPJOB

Attention: If improperly used, the ZAPJOB initialization statement can cause JES2 ABENDs including ABENDs on multiple systems. Be certain to review the entire ZAPJOB documentation before using this initialization statement.

Use ZAPJOB to remove all traces of a job structure from the JES2 job queue. It is intended to be used in situations where a job cannot be removed using normal JES2 commands or by a JES2 restart. Ensure that the job and any output it might have created is not active in any JES2 process or active on a device. Zapping a job that is active can lead to ABENDs and the loss of a PCE until JES2 is restarted. ZAPJOB will not correct queue errors. If the JOB or output queue has an error, a JES2 restart is required to rebuild the job queue.

When specifying a job to zap, IBM® suggests specifying as many operands as are known for that job. This reduces the possibility of accidentally zapping the wrong job because of a typing error.

A $ZAPJOB command can be placed in the initialization data set. This is not the same as using the ZAPJOB initialization statement. A $ZAPJOB command in the initialization data set is processed after JES2 initialization has completed. A ZAPJOB initialization statement removes the job before verifying the job queue. Because of the risk of forgetting to remove it, IBM suggests that you do not place $ZAPJOB commands in the initialization data set.
The ZAPJOB initialization statement can only be entered from CONSOLE mode. This prevents you from forgetting a ZAPJOB statement that you placed into the initialization data, thereby impacting jobs on future JES2 starts. See the JES2 Initialization and Tuning Guide for information on how to enter CONSOLE mode during initialization.
On ZAPJOB, you must specify one of: JOBID=, JOBKEY=, JQEINDEX=, or JQEOFF=.
If a job has a job key of zero (job has not had a job key assigned or has partially purged) you must specify JOBKEY=0, JQEINDEX= or JQEOFF= to "zap" the job.