Output
◆SWAPLIMIT
◆PROCESSLIMIT
◆THREADLIMIT
◆OPENFILELIMIT
The possible UNIX
◆RUNLIMIT
◆FILELIMIT
◆DATALIMIT
◆STACKLIMIT
◆CORELIMIT
If a job submitted to the queue has any of these limits specified (see bsub(1)), then the lower of the corresponding job limits and queue limits are used for the job.
If no resource limit is specified, the resource is assumed to be unlimited. User shell limits that are unlimited are not displayed.
EXCEPTION STATUS Possible values for the exception status of a job include:
idle
The job is consuming less CPU time than expected. The job idle factor
(CPU time/runtime) is less than the configured JOB_IDLE threshold for the queue and a job exception has been triggered.
overrun
The job is running longer than the number of minutes specified by the
JOB_OVERRUN threshold for the queue and a job exception has been triggered.
underrun
The job finished sooner than the number of minutes specified by the
JOB_UNDERRUN threshold for the queue and a job exception has been triggered.
Job Array Summary Information
If you use
JOBID | Job ID of the job array. |
ARRAY_SPEC | Array specification in the format of name[index]. The array specification may be |
| truncated, use |
OWNER | Owner of the job array. |
NJOBS | Number of jobs in the job array. |
PEND | Number of pending jobs of the job array. |
RUN | Number of running jobs of the job array. |
DONE | Number of successfully completed jobs of the job array. |
74Platform LSF Command Reference