I almost agree. My issue is the same as your issue with DRMAA_ERRNO_INVALID_ARGUMENT. The job, DRMAA_JOB_IDS_SESSION_ANY, is valid. It just happens that at the moment there are no valid jobs in the system. A DRMAA_NO_VALID_JOBS error would be more to my liking. It might also apply to drmaa_control(ALL). Daniel Peter Troeger wrote:
For me DRMAA_ERRNO_INVALID_JOB seems to be the right answer, DRMAA_ERRNO_INVALID_ARGUMENT is not appropriate here. The 'DRMAA_JOB_IDS_SESSION_ANY' argument of the call is valid in any case, but the empty set of job id's thereby identified is the problem. You could think of an error like DRMAA_ERRNO_INVALID_SESSION, but this may be overkill.
Regards, Peter.
Daniel Templeton schrieb:
What happens when I call drmaa_wait(ANY) and there are no running or completed jobs? The specs don't address this. Obviously an error code gets returned. Which one? DRMAA_ERRNO_NO_RUSAGE? DRMAA_ERRNO_INVALID_JOB? DRMAA_ERRNO_INVALID_ARGUMENT? DRMAA_ERRNO_EXIT_TIMEOUT? I could make a case for each of them. It looks like the SGE implementation returns DRMAA_ERRNO_INVALID_JOB.
Daniel