Troubleshooting Other Batch System Jobs
| Error type | Where it is logged |
|---|---|
| SSH connection times out | The error is logged in history for the job under job submission and control actions, with a message that connection has timed out. You can access the history through Flow Manager, the jhist command, or IBM Spectrum LSF Application Center. |
| SSH connection successful, but submission and control actions fail on the Other Batch System | The error is logged in history for the job. For job submission, the error message from the standard error output of the submit.sh script is logged in history. For job control, the error message from the standard error output of the query.sh script is logged in history. You can access the history with the jhist command. |
| Job status query fails from jfd to eem.batch. | If the job status query fails for any reason, LOG_DEBUG level error messages are logged in the $JS_LOGDIR/log/jfd.log.host_name file. |
| Error and debug messages for eem.batch | Error and debug messages for the eem.batch of each configured batch system are logged in $JS_LOGDIR/log/eem.otherbatch.log.batch_system_name. The batch system name is the directory name for that batch system under $JS_ENVDIR/other_batch. |