man page(1) manual page

NAME

bqueues - get information about batch queues in the lsbatch system

SYNOPSIS

bqueues [ -h ] [ -V ] [ -w | -l ]
[ -m host_name ] [ -u user_name ] [ queue_name ... ]

Display the status and other information about the batch queues queue_name .... The default is to return information about all queues in the system. Batch queue names and characteristics are set up by the LSF administrator (see lsbatch(5) and mbatchd(8) ). A listing of the queues is displayed with the following fields:

QUEUE_NAME
The name of the queue.

PRIO The priority of the queue. It determines the order in which the job queues are searched at job dispatch, suspension and resumption time. Queues with higher priority values are searched first (this is contrary to UNIX process priority ordering) for job dispatch and resumption, and are searched last for job suspension.

NICE The nice value at which jobs in this queue will be run. This is the UNIX nice value for reducing the process priority (see nice(1) ).

STATUS
The current status of the queue. Possible values are :

Open The queue is able to accept jobs.

Closed
The queue is not able to accept jobs.

Active
Jobs in this queue may be started.

Inactive
Jobs in this queue cannot be started for the time being.

At any moment, each queue is either Open or Closed, and is either Active or Inactive. The queue can be opened, closed, inactivated and re-activated by the LSF administrator using the badmin command (see badmin(8) ). The queue can also be set to be inactive when either of its dispatch windows or run windows are closed (see DISPATCH_WINDOWS). In this case the queue cannot be activated using the badmin command. The queue is reactivated by lsbatch when one of its dispatch windows and one of its run windows are open again. The initial state of a queue at lsbatch boot time is set to open, and either active or inactive depending on its windows.

For the long display format (displayed when the -l option is specified), the reason for a queue being Inactive is explained as follows. If the queue is out of either its dispatch windows or run windows, Inact_Win is shown. If the queue has been inactivated by the LSF administrator, Inact_Adm is shown.

MAX The maximum number of jobs that can be dispatched from this queue and have not finished yet (including suspended jobs). If the character `-' is displayed, there is no limit.

JL/U The maximum number of jobs per user that can be dispatched from this queue and that have not finished yet (including suspended jobs). If the character `-' is displayed, there is no limit.

JL/P The maximum number of jobs per processor that can be dispatched from this queue and that have not finished yet (including suspended jobs). This limit controls the number of jobs sent to each host. The limit is configured per processor so that multiprocessor hosts are automatically allowed to run more jobs. If the character `-' is displayed, there is no limit.

NJOBS
The total number of jobs currently in this queue, including pending, running, and suspended jobs. A parallel job that is running on n processors is counted as one job, since it only takes one job slot in the queue. See bjobs(1) for an explanation of batch job states.

PEND The number of pending jobs in this queue.

RUN The number of running jobs in this queue.

SUSP The number of suspended jobs in this queue.

OPTIONS

-h Print command usage to stderr and exit.

-V Print LSF release version to stderr and exit.

-w Display queue information in a wide format. Fields are displayed without being truncated.

-l Display queue information in a (long) multi-line format. The following information is given in addition to the display fields previously described :

DESCRIPTION: A description of the typical use of the queue.
SSUSP: The number of jobs in the queue that are suspended by the lsbatch system.
USUSP: The numbers of jobs in the queue that are suspended by the job submitter or by the LSF administrator.
RESOURCE LIMITS: The per-process UNIX hard resource limits for all the processes that belong to a job in this queue (see getrlimit(2) and lsbatch(5) ). Possible resource limits defined for a queue are: CPULIMIT, FILELIMIT, DATALIMIT, STACKLIMIT, CORELIMIT, and MEMLIMIT. If a job submitted to this queue has any of those limits specified (see bsub(1) ), then the lower of the corresponding job and queue limits is used for the job. The default values for the resource limits are infinity.
SCHEDULING PARAMETERS: The loadSched and loadStop vectors for controlling batch job dispatch, suspension, and resumption in combination with those of hosts (see bhosts(1) and lsbatch(5) ).

The loadSched and loadStop vectors have the following fields:

r15s
The 15-second exponentially averaged effective CPU run queue length.

r1m
The 1-minute exponentially averaged effective CPU run queue length.

r15m
The 15-minute exponentially averaged effective CPU run queue length.

ut: The CPU utilization exponentially averaged over the last minute, between 0 and 1.
pg: The memory paging rate exponentially averaged over the last minute, in pages per second.
io: The disk I/O rate exponentially averaged over the last minute, in Kbytes per second.
ls: The number of current login users.
it: The idle time of the host (keyboard not touched on all logged in sessions), in minutes.

swp
The amount of currently available swap space, in Mbytes.

mem
The amount of currently available memory, in Mbytes.

tmp
The amount of free space in /tmp, in Mbytes.

In addition to these internal indices, external indices are also displayed if they are defined in lsb.queues (see lsbatch(5) ).

The values in the loadSched vector specify the job dispatching thresholds for the corresponding load indices. If a character `-' is displayed as the value, it means this threshold is don'tcare. Jobs in this queue may be dispatched to a host if the values of all the load indices of the host are within (below or above, depending on the meaning of the load index) the corresponding thresholds of this queue and this host. The same conditions are used to resume jobs dispatched from this queue that have been suspended on this host.

Similarly, the values in the loadStop vector specify the thresholds for job suspension. If any of the load index values on a host goes beyond the corresponding threshold of the queue, jobs in the queue will be suspended.

SCHEDULING POLICIES: Scheduling policies of the queue. Optionally, one or more of the following policies may be configured:
FAIRSHARE: Jobs in this queue are scheduled based on a fairshare policy. In general, a job would be dispatched earlier than other jobs in this queue if the job's owner has more shares (see USER_SHARES below), less running jobs, has used less CPU time in the recent past, and the job has waited longer. If all the users have the same shares, jobs in this queue are scheduled in a round-robin fashion.

If the fairshare policy is not specified, jobs in this queue are scheduled based on the conventional first-come-firstserve (FCFS) policy. That is, jobs submitted earlier to this queue would be dispatched earlier than other jobs in this queue.

PREEMPTIVE: Jobs in this queue may preempt running jobs from lower priority queues. That is, jobs in this queue may still be able to start even though the job limit of a host or a user has been reached, as long as not all of the job slots defined by the job limit are taken by the jobs from those queues whose priorities are not lower than the priority of this queue. Jobs from lower priority queues would be suspended in order to ensure that the number of running jobs (excluding suspended jobs) is within the corresponding job limit. If the preemptive policy is not specified, the default is not to preempt any job.
EXCLUSIVE: Jobs dispatched from this queue can run exclusively on a host if the user so specifies at job submission time (see bsub(1) ). Exclusive execution means that the job is sent to a host with no other batch jobs running there, and no further job, batch and interactive, will be dispatched to that host while the job is running. The default is not to allow exclusive jobs.
USER_SHARES: A list of [username, share] pairs. username is either a user name or a user group name. share is the number of shares of resources assigned to the user or user group. A party will get a portion of the resources according to the party's share divided by the sum of the shares of all parties specified in this queue.
DEFAULT HOST SPECIFICATION: A host name or host model name. The appropriate CPU scaling factor of the host or host model (see lsinfo(1) ) is used to adjust the actual CPU time limit at the execution host (see CPULIMIT in the «lsb.queues file» section of lsbatch(5) ). This specification overrides the system default DEFAULT_HOST_SPEC specified in the lsb.params file (see the «lsb.params file» section of lsbatch(5) ).
DISPATCH_WINDOWS: One or more dispatch windows in a week during which jobs in this queue may be dispatched to run. When a queue is out of its windows, no job in this queue can be dispatched. Jobs already dispatched are not affected by the dispatch windows. The default is no restriction, or always open (that is, 24 hours a day, seven days a week). Note that such windows are only applicable to batch jobs. Interactive jobs scheduled by the Load Information Manager (LIM) of LSF are controlled by another set of dispatch windows (see lshosts(1) ). Similar dispatch windows may be configued for individual batch server hosts (see bhosts(1) ).

A window is displayed in the format of begin_time-end_time. Time is specified in the format of [day:]hour[:minute], where all fields are numbers in their respective legal ranges: 0(Sunday)-6 for day, 0-23 for hour, and 0-59 for minute. The default value for minute is 0 (on the hour). The default value for day is every day of the week. The begin_time and end_time of a window are separated by `-', with no blank characters (SPACE and TAB) in between. Both begin_time and end_time must be present for a window. Windows are separated by blank characters. If only character `-' is displayed, the windows are always open.

RUN_WINDOW: One or more run windows in a week during which jobs in this queue may execute. When a queue is out of its window or windows, no job in this queue will be dispatched. In addition, when the end of a run window is reached, any running jobs from this queue are suspended until the beginning of the next run window when they are resumed. The default is no restriction, or always open.
USERS: A list of names of users and user groups allowed to submit jobs to this queue. User group names have a `/' appended. See bugroup(1) .
HOSTS: A list of names of hosts and host groups to which jobs in this queue can be dispatched. Host group names have a `/' appended. See bmgroup(1) .
NQS DESTINATION QUEUES: The NQS destination queues. A job submitted to this queue will be routed to one of the NQS destination queues and run on an NQS batch server host which is not a member of the LSF cluster. Although running on an NQS system outside the LSF cluster, the job is still managed by the lsbatch in almost the same way as jobs running inside the LSF cluster. Thus, LSF users may have their batch jobs transparently sent to an NQS system to run and get the results of the jobs back. Users may use any supported user interface, including lsbatch commands, lsNQS (the NQS commands; see lsnqs(1) ), and xlsbatch (the GUI for lsbatch users; see xlsbatch(1) ), to submit, monitor, signal and delete their batch jobs that are running in an NQS system. See lsbatch(5) and bsub(1) for more information.

-m host_name
Display the queues from which batch jobs may be dispatched to the host or the host group (see bmgroup(1) ) specified by host_name. The default is to consider all the hosts.

-u user_name
Display the queues to which the user or the user group (see bugroup(1) ) specified by user_name may submit batch jobs. The default is to consider all the users.

queue_name ...
Display information about queue(s) that are specified by queue_name ... . If no queue_name is specified, the default is to display the information about all the queues in the lsbatch system that satisfy the specification of the options -m and/or -u.

NAME

SYNOPSIS

DESCRIPTION

OPTIONS

SEE ALSO