Platform LSF Command Reference - SAS

jobsjob_ID | "job_ID[index]"-h-Vname 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.The -u option cannot be used with the -G option.Displays information about the specified jobs or job arrays.If you use -A, specify job array IDs without the index list.Prints command usage to stderr and exits.Prints LSF release version to stderr and exits.Output: Default DisplayPending jobs are displayed in the order in which they are considered for dispatch. Jobs in higher priority queues aredisplayed before those in lower priority queues. Pending jobs in the same priority queues are displayed in the order inwhich they were submitted but this order can be changed by using the commands btop or bbot. If more than one jobis dispatched to a host, the jobs on that host are listed in the order in which they are considered for scheduling on thishost by their queue priorities and dispatch times. Finished jobs are displayed in the order in which they were completed.A listing of jobs is displayed with the following fields:JOBIDUSERSTATQUEUEFROM_HOSTThe job ID that LSF assigned to the job.The user who submitted the job.The current status of the job (see JOB STATUS below).The name of the job queue to which the job belongs. If the queue to which the jobbelongs has been removed from the configuration, the queue name is displayed aslost_and_found. Use bhist to get the original queue name. Jobs in thelost_and_found queue remain pending until they are switched with the bswitchcommand into another queue.In a MultiCluster resource leasing environment, jobs scheduled by the consumercluster display the remote queue name in the format queue_name@cluster_name. Bydefault, this field truncates at 10 characters, so you might not see the cluster nameunless you use -w or -l.The name of the host from which the job was submitted.82 Platform LSF Command Reference