QMOD(1) General Commands Manual QMOD(1) NAME qmod - modify a Univa Grid Engine queue, running job or job class SYNTAX qmod [ options ] DESCRIPTION Qmod enabled users classified as owners of a running job, queue or job class to modify the state of that object. Users that have submitted a job automatically own the job. Queue and job class ownership is defined by the owner attribute within a queue and by the owner_list attribute defined in the job class (see queue_conf(5) or sge_job_class(5) for details). A manager/operator or root can execute qmod for any object in a Univa Grid Engine but only from administrative hosts. The switches below expect the arguments wc_queue_list, wc_job_list or jc_list that describe the object that should be modified. Find the description for these arguments in sge_types(1). OPTIONS -c wc_job_range_list | wc_queue_list Note: Deprecated, may be removed in future release. Please use the -cj or -cq switch instead. Clears the error state of the specified jobs(s)/queue(s). -cj wc_job_range_list Clears the error state of the specified jobs(s). -cq wc_queue_list Clears the error state of the specified queue(s). -d wc_queue_list Disables the queue(s), i.e. no further jobs are dispatched to disabled queues while jobs already executing in these queues are allowed to finish. -djc jc_list Disables the job class variant(s) that are specified. If only the job class name is specified (without variant name) then only the default variant of a job class will be disabled whereas all other variants remain in their previous state. Job class vari- ants that are in the disabled state cannot be used to create new jobs. -e wc_queue_list Enables the queue(s). -E wc_queue_list Sets queue(s) into error state. -ejc jc_list Enables the job class variant(s) that are specified. If only the job class name is specified (without variant name) then only the default variant of a job class will be disabled whereas all other variants remain in their previous state. Job class vari- ants that are in enabled state can be used to create new jobs. -f Force the modification action for the queue despite the apparent current state of the queue. For example if a queue appears to be suspended but the job execution seems to be continuing the man- ager/operator can force a suspend operation which will send a SIGSTOP to the jobs. In any case, the queue or job status will be set even if the sge_execd(8) controlling the queues/jobs can- not be reached. Requires manager/operator privileges. -help Prints a listing of all options. -msg [message] The -msg switch can be used in combination with other switches of this command that trigger queue state changes. The specified message will be attached to specified queues. If message is omitted then previously attached messages will be deleted. The message string will be displayed by qstat if the -explain m switch is specified for this command. -p jid wc_job_task_list [preemptive_action] Sends a manual preemption request to the Univa Grid Engine sys- tem. The job specified by jid has to be pending and it will be seen as preemptor candidate by the Univa Grid Engine system. All other jobs (or tasks of an array job) specified by wc_job_task_list have to be running and they act as preemptee candidates. The Univa Grid Engine scheduler tries to start the preemptor candidate if there are no other jobs with a higher effective priority. If there are no free resources available then the sys- tem will preempt the preemptee candidates to gain access to the used resources so that the preemptor candidate can be started. The method how preemptee candidates are preempted can be speci- fied by the preemption_action. It can be one of the letters (S)suspend, e(N)handed suspend, (P)reempt, (C)heckpoint, (R)erun or (T)erminate. If the specified preemption action is not avail- able for a preemptee candidate or when the preemption_action is not specified then the system might choose an appropriate pre- emption action to gain required resources. For more detail about preemption and the differences of the pre- emptive actions read sge_preemption(5) -r wc_job_range_list | wc_queue_list Note: Deprecated, may be removed in future release. Please use the -rj or -rq switch instead. If applied to queues, reschedules all jobs currently running in this queue. If applied to running jobs, reschedules the jobs. Requires root or manager privileges. In order for a job to be rescheduled, it or the queue in which it is executing must have the rerun flag activated. (See -r option in the qsub(1) man page and the rerun option in the queue_conf(5) man page for more information.) Additional restrictions apply for parallel and checkpointing jobs. (See the reschedule_unknown description in the sge_conf(5) man page for details). -rj wc_job_range_list If applied to running jobs, reschedules the jobs if they can be rescheduled. See also the -r switch. Requires root or manager privileges. -rq wc_queue_list If applied to queues, reschedules all jobs currently running in this queue. For parallel jobs, the job is rescheduled only if the master task of this parallel job is running in this queue. See also the -r switch. Requires root or manager privileges. -s wc_job_range_list | wc_queue_list Note: Deprecated, may be removed in future release. Please use the -sj or -sq switch instead. If applied to queues, suspends the queues and any jobs which might be active. If applied to running jobs, suspends the jobs. -si session_id Requests sent by this client to the sge_qmaster(1) daemon will be done as part of the specified session. If the switch is omit- ted or if NONE is specified as session_id then such requests will be executed outside the control of a session. Find more information concerning sessions in session_conf(5). -sj wc_job_range_list If applied to running jobs, suspends the jobs. For parallel jobs, Univa Grid Engine sends the STOP signal to the master task only. The master task has to handle the suspending of all slave tasks itself then. This is because Univa Grid Engine doesn't know in which order the slave tasks have to be suspended. If a job is both suspended explicitly and via suspension of its queue, a following unsuspend of the queue will not release the suspension state on the job. -sq wc_queue_list If applied to queues, suspends the queues and any jobs which might be active. For parallel jobs, Univa Grid Engine sends the STOP signal to the master task only (see -sj switch). If any slave task of a parallel job runs in a queue that is to be sus- pended, the master task of this job is suspended, no matter where it is running. -us wc_job_range_list | wc_queue_list Note: Deprecated, may be removed in future release. Please use the -usj or -usq switch instead. If applied to queues, unsuspends the queues and any jobs which might be active. If applied to jobs, unsuspends the jobs. For parallel jobs, please see the -usj or -usq switch. -usj wc_job_range_list If applied to jobs, unsuspends the jobs. For parallel jobs, Univa Grid Engine sends the CONT signal to the master task only. The master task has to handle the unsuspending of all slave tasks itself then. If a job is both suspended explicitly and via suspension of its queue, a following unsuspend of the queue will not release the suspension state on the job. A parallel job is not un-suspended as long as at least one task of this job is suspended for any reason. -usq wc_queue_list If applied to queues, unsuspends the queues and any jobs which might be active. For parallel jobs, Univa Grid Engine sends the CONT signal to the master task only (see -usj switch). A paral- lel job is not unsuspended as long as at least one task of this job is suspended for any reason. ENVIRONMENTAL VARIABLES SGE_ROOT Specifies the location of the Univa Grid Engine standard config- uration files. SGE_CELL If set, specifies the default Univa Grid Engine cell. To address a Univa Grid Engine cell qmod uses (in the order of precedence): The name of the cell specified in the environment variable SGE_CELL, if it is set. The name of the default cell, i.e. default. SGE_DEBUG_LEVEL If set, specifies that debug information should be written to stderr. In addition the level of detail in which debug informa- tion is generated is defined. SGE_QMASTER_PORT If set, specifies the tcp port on which sge_qmaster(8) is expected to listen for communication requests. Most installa- tions will use a services map entry for the service "sge_qmas- ter" instead to define that port. FILES //common/act_qmaster Univa Grid Engine master host file SEE ALSO sge_intro(1), sge_ckpt(1), qstat(1), queue_conf(5), session_conf(5), sge_preemption(5), sge_execd(8), sge_types(1), sge_job_class(5). COPYRIGHT See sge_intro(1) for a full statement of rights and permissions. Univa Grid Engine User Commands UGE 8.5.4 QMOD(1)