Hi DRMAA experts -
IIRC, last time I looked into DRMAA it used ephemeral job ids - in other words, when submitting a job via DRMAA you got back a handle to the job, but this handle was meaningless across a restart of the application (similar to a file descriptor). So if application X submits a job and then application X is restarted (e.g. the submit machine is rebooted), there was no guarantee that X could continue to monitor/manage the job. Is the above still true? If so, is there a well-known work-around and/or are there plans to address the issue in a future DRMAA spec? Thanks much, Todd -- Todd Tannenbaum University of Wisconsin-Madison Center for High Throughput Computing Department of Computer Sciences -- drmaa-wg mailing list [email protected] https://www.ogf.org/mailman/listinfo/drmaa-wg
