Exit codes
If the proxy LSF® job fails, you can determine the location of the failure by the exit code specified in the job details, as follows:
The following exit codes may occur if there is a problem between your LSF proxy job and the mainframe job:
Exit Code |
Failure Reason |
|---|---|
230 |
Failed to connect to mainframe via FTP. |
231 |
Failed to log in to mainframe. |
232 |
Command site filetype=jes or site filetype=seq failed. |
233 |
Failed to retrieve job ID. put or get command failed. |
234 |
Failed to retrieve job output. |
235 |
Failed to match Dir Header. Dir command failed. |
236 |
Failed to get job status. Dir command failed. |
237 |
Timeout checking mainframe job status. |
238 |
Failed to delete a mainframe job. |
239 |
Encryption error. |
240 |
Environment variable not found. |
241 |
Script error. |
242 |
LSF configuration file not found. |
243 |
FTP configuration file not found. |
244 |
Incomplete system output file: IEF142I and IEF472I not found. |
245 |
System output file not found. |
246 |
bpost command failed. |
247 |
bread command failed. |
248 |
Failed to get mainframe job ID from bread output. |
249 |
Failed to transfer JCL file from z/OS® host to LSF host. |
250 |
Failed to modify job name in JCL file. |
255 |
Mainframe job has an ABEND status. |
A template file should contain all of the information needed by the end user to define a job for use in a specific application. The template you create should use simple, recognizable terms, and can contain help for some or all fields. You can use the template to highlight only those fields where user input is critical, and allow all others to use the default values. This can be useful for simplifying complex submission options.
This procedure demonstrates how to take a job submission command for an application and translate it into a template using the following command, which submits a blast job that searches a database for matches:
blastall.exe -p blastp -d "human" -e 11.02 -o "c:\tmp\zzz.txt" -F T -S 2 -T F -1 -U F
In the above example, blastall.exe is the executable, and the remaining values are parameters that describe how to run the executable: -p blastp specifies the BLAST search to run, -d human specifies the database to search, and so on.