| Previous | Contents |
The MOTIF Editor/Monitor allows the manual submission of jobs. This method lets the user test the execution of the jobs in the job group when it is created and to submit it at any time if necessary. The job may also be stopped, suspended and resumed at any time (see subsequent sections).
In order to submit a job for execution, select the submit job icon and
click on the job to be submitted. See Section 3.1.1.1 for details on how
to select the job. The job will be submitted immediately and may be
monitored as it triggers all dependent jobs. See Section 2.10.2 for
details on setting up the submit parameters.
3.2.6 Stop job
Once a job has started, either manually or automatically, it may be terminated using the stop icon. The job must be either in the K queue(submitted for execution) or the L queue(execution started). Stopping the job will cause it to terminate with a failure status. The resulting failure messages will be sent automatically.
In order to terminate a job during execution select the stop job icon and click on the job to be stopped. See Section 3.1.1.1 for details on how to select the job. The job will terminate immediately and all subsequent dependencies will not execute.
The ability to stop the execution of a job in the K or L queues is dependent on a number of factors. The first and most important of these is the performance and complexity of the system. The ability of the icon to reflect the current state of the queue is dependent on a latency that may occur as the queue state is updated in a multiple cluster or remote server environment. Another factor that may cause a difficulty in aborting the job is that if a job does not perform DCL commands, it may not be stopped. Usually, jobs that have a designated delay in the K and L queues and perform some DCL commands are able to be aborted using the stop function. |
A job may be suspended temporarily if it has been submitted for execution either manually or automatically. This has the effect of holding the job up if it is in the execution queues. However if the job is in the scheduling queues it will be stopped and may not be restarted. The resume job icon (described in the next section) will restart the queue.
In order to suspend a job during execution, select the suspend job icon and click on the job to be suspended. See Section 3.1.1.1 for details on how to select the job. The job will be suspended until restarted with the resume icon.
The ability to suspend the execution of a job in the K or L queues is dependent on a number of factors. The first and most important of these is the performance and complexity of the system. The ability of the icon to reflect the current state of the queue is dependent on a latency that may occur as the queue state is updated in a multiple cluster or remote server environment. Another factor that may cause a difficulty in suspending the job is that if a job does not perform DCL commands, it may not be stopped. Usually, jobs that have a designated delay in the K and L queues and perform some DCL commands are able to be aborted using the suspend function. |
| Previous | Next | Contents |