(hold job)
Synopsis
qhold [{-h <HOLD LIST>|-t <array_range>}] <JOBID>[ <JOBID>] ...
Description
The qhold command requests that the server place one or more holds on a job. A job that has a hold is not eligible for execution. There are three supported holds: USER, OTHER (also known as operator), and SYSTEM.
A user may place a USER hold upon any job the user owns. An "operator", who is a user with "operator privilege," may place ether an USER or an OTHER hold on any job. The batch administrator may place any hold on any job.
If no -h option is given, the USER hold will be applied to the jobs described by the job_identifier operand list.
If the job identified by job_identifier is in the queued, held, or waiting states, then the hold type is added to the job. The job is then placed into held state if it resides in an execution queue.
If the job is in running state, then the following additional action is taken to interrupt the execution of the job. If checkpoint/restart is supported by the host system, requesting a hold on a running job will (1) cause the job to be checkpointed, (2) the resources assigned to the job will be released, and (3) the job is placed in the held state in the execution queue.
If checkpoint/restart is not supported, qhold will only set the requested hold attribute. This will have no effect unless the job is rerun with the qrerun command.
Options
Operands
The qhold command accepts one or more job_identifier operands of the form:
sequence_number[.server_name][@server]
Example
> qhold -h u 3233 place user hold on job 3233 |
Standard error
The qhold command will write a diagnostic message to standard error for each error occurrence.
Exit status
Upon successful processing of all the operands presented to the qhold command, the exit status will be a value of zero.
If the qhold command fails to process any operand, the command exits with a value greater than zero.
Related topics
Non-Adaptive Computing topics
© 2012 Adaptive Computing