Here is the latest update status for the Wiki:
As promised on the call, here's the summary of the monitoring discussion. Please add your comments and corrections.
o The monitoring session is should provide parallel functionality to the job session's job monitoring for monitoring all jobs in the cluster.
sequence<Job> MonitoringSession::getAllJobs(JobInfo filter);
o The job monitoring capability for the monitoring session should support a query filter
See above. Will be discussed on the call.
o The job monitoring capability for the monitoring session will return a set of job objects that contain a set of core information and a dictionary of optional information that will be "standardized" through the drmaa.org site.
This is modeled similar as in the JobTemplate struct: struct JobInfo { ... readonly attribute Dictionary drmsSpecific; }
o The job monitoring capability should be able to return jobs from any/all users. o The DRM or DRMAA implementation is at liberty to restrict the set of returned jobs based on site or system policies, such as security settings.
The description of MonitoringSession was updated accordingly.
o The job monitoring model will assume that the DRM system has three job information states: running, buffered, purged. Only information for jobs that are still running or are still held in the buffer of finished job information will be reported. Jobs that have been purged out to accounting will be ignored. o Exit status will be an optional component of the job object. It will only be available for jobs still held in the DRM system's buffer.
The description of JobInfo was updated accordingly. Best, Peter.