When all tasks finish, Session Scheduler exits, all temporary files are deleted, the session job is cleaned from the system, and Session Scheduler output is captured and included in the standard LSF job e-mail.
You can also submit a Session Scheduler job without a task definition file to specify a single task.
See the ssched command reference for detailed information about all task options.
The index list must be enclosed in square brackets. The index list is a comma-separated list whose elements have the syntax start[-end[:step]] where start, end and step are positive integers. If the step is omitted, a step of one (1) is assumed. The task array index starts at one (1).
All tasks in the array share the same option parameters. Each element of the array is distinguished by its array index.
See the ssched command reference for detailed information about all task options.
-Q enables automatic task requeue and sets the LSB_EXIT_REQUEUE environment variable. Use spaces to separate multiple exit codes. LSF does not save the output from the failed task, and does not notify the user that the task failed.
If a job is killed by a signal, the exit value is 128+signal_value. Use the sum of 128 and the signal value as the exit code in the parameter. For example, if you want a task to rerun if it is killed with a signal 9 (SIGKILL), the exit value is 128+9=137.
The SSCHED_REQUEUE_LIMIT setting limits the number of times a task can be requeued.
See the ssched command reference for detailed information about all task options.
ssched exits after the check is complete. An exit code of 0 indicates no errors were found. A non-zero exit code indicates errors. You can run ssched -C outside of LSF.
See the ssched command reference for detailed information about all task options.
By default, Session Scheduler sessions are unrecoverable. In the event of a system crash, the session job must be resubmitted and all tasks are resubmitted and rerun.
However, the Session Scheduler supports application-level checkpoint/restart using Platform LSF's existing facilities. If the user specifies a checkpoint directory when submitting the session job, the job can be restarted using brestart. After a restart, only those tasks that have not yet completed are resubmitted and run.