The run table of the rd_lsf database provides the linkage between the jobId and rank values in the rd_lsf database tables. It also provides the LSF ID values for the individual jobs that were run together with their preexec and callback job LSF ID values along with various time stamps associated with the job execution and the job return code. The columns in this table are:
- jobId - The job ID value. This is the key that links this data to the entries in the job table of the rd_lsf database and the runScripts table of the rd_workflow database
- rank - The job rank identifier. I do not know what this filed is used for but it is incremented each time a new job is run even if it is a rerun of an existing jobId
- lsfId - The LSF job ID of the batch job running the main job process. This job is submitted with a hold until the preexec job is completed
- preExecId - The LSF job ID of the preexec script that runs before the main job. Submitted after the main job with a hold
- callbackId - The LSF job ID of the callback step to be executed after the main job. This is submitted with a hold until the main job is completed. Once this job is submitted, the hold on the preexec job is lifted so processing can start
- status - The current status of the job. Possible states are 'finished', 'processing', and 'pending' (There might be others)
- attemptTime - The time the job first entered the system
- submitTime - The time the job was submitted to LSF
- startTime - The time the main job was started (This might be the time the preexec job starts, need to check)
- stopTime - The time the main job completed (This might be the end time of the callback job)
- returnCode - The return code from the LSF batch job running the main execution job