9.10 Killing the jobnets and the jobs being executed
This subsection describes the procedure for killing the execution of jobnets and jobs.
You can also use the ajskill command to kill the execution of jobnets and jobs. For details of the command, see the description of ajskill in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
To kill the execution of a jobnet:
-
In the JP1/AJS3 - View window, in Function Menu, click Status Monitor.
Status Monitor is now selected.
-
In the tree area, click the job group that manages the jobnet or job whose execution you want to kill.
The job group you clicked is now selected.
The root jobnet appears in the list area.
-
Click the target jobnet or the jobnet that manages the target job, choose View, Daily Schedule, and then Hierarchy.
The Daily Schedule (Hierarchy) window appears.
-
In the tree area, click the target jobnet or job.
The jobnet or job you clicked is now selected.
-
For the jobnet or job you selected in step 4, in the schedule area, click the colored mark for which you want to kill execution. Alternatively, in the execution result list, click the line for which you want to kill execution.
-
Choose Operations and then Kill.
A confirmation dialog box asking whether you want to kill the jobnet or job appears.
-
Click the Yes button.
The execution of the jobnet or job is killed.
The colored mark in the schedule area is displayed in pale red (default), which indicates the killed status.
The change is also reflected in the execution result list.
- Cautionary notes
-
-
You can kill the execution of jobnets whose status is Now running, Running + Warning, Running + Abend, or Now monitoring only.
-
You can kill the execution of jobs whose status is Now queuing or Now running only. For queueless jobs, you can also kill the jobs whose status is Waiting to execute.
-
For details about how to kill a jobnet for which start conditions are being monitored, see 8.1.1 Stopping a jobnet that is monitoring start conditions in the JP1/Automatic Job Management System 3 Administration Guide.
-
When you kill a jobnet, communications are exchanged and the database in JP1/AJS3 is updated. Therefore, if you select many jobnets and kill all of them at one time, the overall burden on JP1/AJS3 is severe, and is likely to adversely affect operation due to processing delays and other problems. If you want to kill multiple jobnets, insert a pause of a few seconds to a few minutes after each time a jobnet is killed.
Note that when you kill a jobnet containing many event jobs or kill multiple jobnets containing event jobs at one time, the restrictions set for successive execution of the ajskill command take effect for the number of event jobs that end because they are killed. For details, see B.8 Limits for the event/action control in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
-
If you kill a job being executed in the Windows environment, the resources used by the job may not be released. We recommend that you end a job using the method recommended by the application that executes the job.
-
- Supplementary notes
-
-
If there is an executing job when the interrupt for the jobnet execution is requested, the job is killed first then the jobnet is interrupted.
-
You can also kill the execution of a jobnet in the following windows:
- JP1/AJS3 - View window (Main window)
- JP1/AJS3 - View window (Summary Monitor window)
- Monthly Schedule window
- Jobnet Monitor window
- Search window
-
You can also kill the execution of a job in the following windows:
- JP1/AJS3 - View window (Summary Monitor window)
- Daily Schedule (All Jobs) window
- Monthly Schedule window
- Jobnet Monitor window
- Search window
-
For details about how to re-execute jobnets and jobs that have been killed, see 9.11 Re-executing jobnets and jobs.
-