On 02/06/16 04:59, Riccardo Murri wrote:
Hi Gizo,

thanks for the suggestion!

However torque has a feature not to immediately remove a completed job from
memory, but keep it for some configurable amount of time so that the qstat
command can display its utilization, including an exit status. This feature
is not a default in torque server and should be configured (option
keep_completed)
http://docs.adaptivecomputing.com/torque/6-0-1/help.htm#topics/torque/2-jobs/keepingCompletedJobs.htm?Highlight=keep_completed.
[...]
The command qstat -f displays the job exit status

qstat -f 1097122
.....
   etime = Wed Jun  1 22:02:27 2016
     exit_status = 0
     submit_args = abc
....
Can you please provide me with the full `qstat -f` output for a
completed job?

It's worth mentioning that i) qstat -f will only work if the job is still in the queue (queued, running, or completed); ii) by default, jobs are removed from the queue as soon as they're completed.

So, although 'qstat -f' is an alternative you can certainly support, it's not general enough to work with a 'standard' Torque setup.

A possible alternative is that GC3Pie submits an epilogue script for each job it submits, to capture the exit code (& more) of the job...

See http://docs.adaptivecomputing.com/torque/4-1-4/Content/topics/12-appendices/perJobPrologueAndEpliogueScripts.htm


regards,

Kenneth

Reply via email to