Use -sto specify a signal number; when the run window closes, the job is signalled by this signal instead of being suspended.
-slaservice_class_name
Specifies the service class where the job is to run.
If the SLA does not exist or the user is not a member of the service class, the job is rejected.
If EGO-enabled SLA scheduling is configured with
ENABLE_DEFAULT_EGO_SLA in lsb.params, jobs submitted without -slaare attached to the configured default SLA.
You can use -gwith -sla. All jobs in a job group attached to a service class are scheduled as SLA jobs. It is not possible to have some jobs in a job group not part of the service class. Multiple job groups can be created under the same SLA. You can submit additional jobs to the job group without specifying the service class name again.
TIP: You should submit your jobs with a runtime limit (-W option) or you should specify a run time limit in a queue or application profile (RUNLIMIT in the queue definition in lsb.queues or RUNLIMIT in the application profile definition in lsb.applications). If you do not specify a run time limit, LSF automatically adjusts the optimum number of running jobs according to the observed run time of finished jobs.
Use bsla to display the properties of service classes configured in LSB_CONFDIR/cluster_name/configdir/lsb.serviceclasses (see lsb.serviceclasses(5)) and dynamic information about the state of each service class.
-sppriority Specifies user-assigned job priority which allow users to order their jobs in a queue. Valid values for priority are any integers between 1 and MAX_USER_PRIORITY (configured in lsb.params, displayed by bparams -l). Job priorities that are not valid are rejected. LSF and queue administrators can specify priorities beyond
MAX_USER_PRIORITY.
The job owner can change the priority of their own jobs. LSF and queue administrators can change the priority of all jobs in a queue.
Job order is the first consideration to determine job eligibility for dispatch. Jobs are still subject to all scheduling policies regardless of job priority. Jobs with the same priority are ordered first come first served.
User-assigned job priority can be configured with automatic job priority escalation to automatically increase the priority of jobs that have been pending for a specified period of time (JOB_PRIORITY_OVER_TIME in lsb.params).
When absolute priority scheduling is configured in the submission queue (APS_PRIORITY in lsb.queues), the user-assigned job priority is used for the JPRIORITY factor in the APS calculation.
-Tthread_limit Sets the limit of the number of concurrent threads to thread_limit for the whole job. The default is no limit.
Exceeding the limit causes the job to terminate. The system sends the following signals in sequence to all processes belongs to the job: SIGINT, SIGTERM, and
SIGKILL.
