switches unfinished jobs from one queue to another
Switches one or more of your unfinished jobs to the specified queue. LSF administrators and root can switch jobs submitted by other users.
By default, switches one job, the most recently submitted job, or the most recently submitted job that also satisfies other specified options (-m, -q, -u, or -J). Specify 0 (zero) to switch multiple jobs.
The switch operation can be done only if a specified job is acceptable to the new queue as if it were submitted to it, and, in case the job has been dispatched to a host, if the host can be used by the new queue. If the switch operation is unsuccessful, the job stays where it is. Switched jobs use the successful application exit values (that is, the exit codes specified by SUCCESS_EXIT_VALUES) from the new queue.
If the parameter DEFAULT_USER_GROUP in lsb.params is defined, a job switched to a queue where it cannot run (without shares in a fairshare queue, for example) is transferred to the default user group so the job can run.
If a switched job has not been dispatched, then its behavior is as if it were submitted to the new queue in the first place.
If a switched job has been dispatched, then it is controlled by the loadSched and loadStop vectors and other configuration parameters of the new queue, but its nice value and resource limits remain the same. Also, the switched job is controlled by the PRIORITY and RUN_WINDOW configuration parameters of the new queue.
Members of a chunk job can be switched to another queue. Running chunk job members are removed from the chunk and switched; all other WAIT jobs are requeued to PEND. For chunk jobs in WAIT state, only the WAIT job is removed from the chunk and switched, and requeued to PEND.
The bswitch command is useful to change a job’s attributes inherited from the queue.
bswitch can switch resizable jobs between queues regardless of job state. Once the job is switched, the parameters in new queue apply, including threshold configuration, run limit, CPU limit, queue-level resource requirements, etc. Multi-phase rusage string resource requirements can be switched in the middle of a phase.
When switching a job between fairshare queues using decayed run time to calculate dynamic priority, the decayed run time is switched. If the old queue did not decay the run time, the non-decayed run time is switched over; if the new queue does not decay run time, the undecayed run time is switched over.
When switching a pending job to a queue with limits set by the parameter RESRSV_LIMIT in lsb.queues, the job’s rusage values must be within the set limits or the job cannot be switched. When switching a running job to a queue with limits set by the parameter RESRSV_LIMIT, the job’s maximum rusage values cannot exceed the maximums set by RESRSV_LIMIT, but the job’s rusage values can be lower than the minimum values.
By default, the job's effective resource requirements are not changed when running bswitch. The effective resource requirement string for scheduled jobs represents the resource requirement used by the scheduler to make a dispatch decision. If the BSWITCH_MODIFY_RUSAGE parameter is enabled and you run bswitch, the job's effective resource requirements are changed according to the new combined resource requirements.
When switching a job that has been auto-attached to a guarantee service class, the auto-attachment is re-evaluated if required.
(Zero). Switches multiple jobs. Switches all the jobs that satisfy other specified options (-m, -q, -u and -J).
Only switches jobs that have the specified job name.
The job name can be up to 4094 characters long. Job names are not unique.
The wildcard character (*) can be used anywhere within a job name, but cannot appear within array indices. For example job* returns jobA and jobarray[1], *AAA*[1] returns the first element in all job arrays with names containing AAA, however job1[*] will not return anything since the wildcard is within the array index.
Only switches jobs dispatched to the specified host, host group, or compute unit.
Only switches jobs in the specified queue.
Only switches jobs submitted by the specified user, or all users if you specify the keyword all. To specify a Windows user account, include the domain name in uppercase letters and use a single backslash (DOMAIN_NAME\user_name) in a Windows command line or a double backslash (DOMAIN_NAME\\user_name) in a UNIX command line.
If you specify a user group, switches jobs submitted by all users in the group.
Required. Specify the queue to which the job is to be moved.
Switches only the specified jobs.
Prints command usage to stderr and exits.
Prints LSF release version to stderr and exits.
You cannot switch a MultiCluster job.
bqueues, bhosts, bugroup, bsub, bjobs