Hello,
We are curious if there are any workarounds to the inability of PBS hooks to send custom messages to STDOUT where a user initiated a “qsub” from.
Currently, a rejected event can send custom messages, but we have several use cases for sending custom messages where the event is accepted. Any assistance that might help would be appreciated.
Thanks,
Sam
You don’t want the message to go to qsub’s stdout. That is often used by scripts to learn the submitted jobid.
As an ugly, untested hack, you could put a wrapper around qsub. When the qsub succeeds, the wrapper could do a qstat looking for a value for the job’s “site” resource (which is normally unused). If the wrapper finds something, it outputs that to stderr. The hook’s job is then to set the text of the site resource to whatever custom message you want.
I suspect, though, that extra messages from qsub will mostly just annoy users and be ignored.
Thanks for confirming the wrapper script approach, however, I do think we need to rethink our core messaging strategy. Maybe an email to the user from the hook might be best solution here.