Update,
After some testing, it appears that the comment may not be very well suited for this. Using the comment I cannot differentiate between jobs, which will run later (when resources are freed by presently running jobs), and jobs, which just ask for more resources, than what is available on any present node.
In both cases, the comment will look like:
Not Running: Insufficient amount of resource:
If I clearly request too many nodes (more than what is available totally), the comment becomes:
Can Never Run: Not enough total nodes available
where it is clearly feasible to delete the job.
Thus, I wonder about alternative ways to do this (still without actually writing a HOOK to run at submission):
As we run a small cluster with a very limited number of jobs in the queue at any time, I could estimate the job start time (set server est_start_time_freq) often (eg every scheduling cycle), and then purge jobs, which do not have a set estimated start time?
Any ideas?
Thanks,
/Bjarne
PS: Presently, there seems to be an issue with estimating the start times, see Qmgr -c 'set server est_start_time_freq ...' fails but hopefully that can be resolved.