The job submission form
You use a job submission form to submit your job to IBM Spectrum LSF. The Generic job submission form is useful when applications are not installed on the system to quickly run an executable binary or script by uploading it to the server and running it.
When you do not specify any options on the job submission form, the job is submitted to the default queue configured in the submission form (normal on the Generic submission form).
You can choose to be notified when your job status changes
Job status change notifications are only visible when the administrator enabled job status change notifications with the parameter ENABLE_JOB_NOTIFICATION=Y in the configuration file $GUI_CONFDIR/pmc.conf.
When you submit a job, you can choose for the system to notify you when the job status changes.
Administrators can also set a default job status change notification for all jobs in the System & Settings tab, .
You can save settings for job submission
You can choose to save any settings you specified for job submission by selecting Save As and saving the submission form under a different name.
You can specify input files for jobs
In the submission form, you can specify input files. Specify files that are locally stored on your computer, files that are already on the server, or even files that do not yet exist. For files that do not exist, use the variables %J for the job ID or %I for the job array index.
Local file
You can upload a file that is locally on your computer for a job. When you upload a file from disk, the file is not uploaded until you click Submit. As a result, you see {$JOBDIRECTORY} in the path. When you click Submit, a temporary directory is created for the job and the file you specified is copied to it.
Server file
You can use a file that was previously uploaded to the web server.
Non-existent files
You can specify files that do not yet exist as input to your job. For example, if your job depends on another job's output file. However, the file must exist when your job starts running or your job fails.
If you use the special character %J in the name of the file, %J is replaced by the job ID of the job.
If you use the special character %I in the name of the file, %I is replaced by the index of the job in the array if the job is a member of an array. Otherwise, %I is replaced by 0 (zero).
You can specify output and error files for jobs
In your submission form, you can specify the location of output and error files. The location must be on the web server. You can specify files that do not yet exist provided that the path is correct.
If you use the special character %J in the name of the file, %J is replaced by the job ID of the job.
If you use the special character %I in the name of the file, %I is replaced by the index of the job in the array if the job is a member of an array. Otherwise, %I is replaced by 0 (zero).
Your data is in the job directory
The job directory is the directory in which job data is located. The job directory is created automatically when you submit the job. The administrator can configure a submission form to allow users to specify a custom job directory.
By default, if the job is submitted with a job name, the job directory is named with the job name, the time stamp, and five random characters in the form: jobname_timestampfiverandomcharacters.
By default, if the job is submitted without a job name, the job directory is named with the application name, the time stamp, and five random characters in the form: applicationname_timestampfiverandomcharacters.
The administrator can configure a submission template to allow users to specify a custom job directory. In such a case, the job directory is the directory that is specified by the user. For more information, see Enabling custom job directories in submission templates.