[DRMAA-WG] Comments on latest DRMAA documents

[Piotr Domagalski]

On 7/27/07, Daniel Templeton <Dan.Templeton at sun.com> wrote:

> Submitting a job creates a record in the session context.  When that job
> ends, that job's status can be permanently set in the record as DONE or
> FAILED.  When the job is reaped, the record is reaped.  Now, before a
> job has finished, or when querying a job from outside the submitting
> session, the drmaa_job_ps routine must talk to the DRM to get the job's
> status.  After a job has finished, the DRM is allowed to claim the job
> doesn't exist.  As long as you're in the same session that submitted the
> job, and you haven't reaped the job, you can use the job's session
> record instead of asking the DRM.  If the job has been reaped or you're
> not in the same session, if the DRM doesn't know about the job, you get
> an INVALID_JOB.  If the DRM always knows about every job that was ever
> submitted, then you'll never get an INVALID_JOB, even if the job has
> been reaped.

Thanks! This explanation made it more clear than any spec before. We'd
love to see something like this in the documents.

-- 
Piotr Domagalski