Defines | |
| #define | DRMAA_TIMEOUT_WAIT_FOREVER -1 |
| #define | DRMAA_TIMEOUT_NO_WAIT 0 |
| #define | DRMAA_PS_UNDETERMINED 0x00 |
| #define | DRMAA_PS_QUEUED_ACTIVE 0x10 |
| #define | DRMAA_PS_SYSTEM_ON_HOLD 0x11 |
| #define | DRMAA_PS_USER_ON_HOLD 0x12 |
| #define | DRMAA_PS_USER_SYSTEM_ON_HOLD 0x13 |
| #define | DRMAA_PS_RUNNING 0x20 |
| #define | DRMAA_PS_SYSTEM_SUSPENDED 0x21 |
| #define | DRMAA_PS_USER_SUSPENDED 0x22 |
| #define | DRMAA_PS_USER_SYSTEM_SUSPENDED 0x23 |
| #define | DRMAA_PS_DONE 0x30 |
| #define | DRMAA_PS_FAILED 0x40 |
| #define | DRMAA_CONTROL_SUSPEND 0 |
| #define | DRMAA_CONTROL_RESUME 1 |
| #define | DRMAA_CONTROL_HOLD 2 |
| #define | DRMAA_CONTROL_RELEASE 3 |
| #define | DRMAA_CONTROL_TERMINATE 4 |
| #define | DRMAA_JOB_IDS_SESSION_ANY "DRMAA_JOB_IDS_SESSION_ANY" |
| #define | DRMAA_JOB_IDS_SESSION_ALL "DRMAA_JOB_IDS_SESSION_ALL" |
| #define DRMAA_CONTROL_HOLD 2 |
HOLD signal. A job can be held if it is in the QUEUED_ACTIVE state, and on SUCESS will enter the USER_ON_HOLD state.
| #define DRMAA_CONTROL_RELEASE 3 |
RELEASE signal. Release a previously held job, only jobs in the USER_ON_HOLD state cen be released. On SUCCESS the job will enter the QUEUED_ACTIVE state.
| #define DRMAA_CONTROL_RESUME 1 |
RESUME signal. A previously stopped job will be resumed. If re-start files are provided the job will used them to re-start execution from the last checkpointing context.
| #define DRMAA_CONTROL_SUSPEND 0 |
SUSPEND signal. A job will be stopped, and restart files transferred back to the client. These files if provided by the running job will be used on RESUME to re-start execution.
| #define DRMAA_CONTROL_TERMINATE 4 |
TERMINATE signal. The job will be killed, it execution can be synchronized through the drmaa_wait() and drmaa_synchronize() function calls. However, job rusage information will not be available and these functions will return DRMAA_ERRNO_NO_RUSAGE.
| #define DRMAA_JOB_IDS_SESSION_ALL "DRMAA_JOB_IDS_SESSION_ALL" |
Pre-defined string used to refer to ALL the jobs submitted during a DRMAA session. Please note that "disposed" jobs will be removed from the job-list associated to the DRMAA session.
| #define DRMAA_JOB_IDS_SESSION_ANY "DRMAA_JOB_IDS_SESSION_ANY" |
Pre-defined string used to refer to ANY job submitted during a DRMAA session. Please note that "disposed" jobs will be removed from the job-list associated to the DRMAA session.
| #define DRMAA_PS_DONE 0x30 |
DONE Job state. Job has been completely executed and output files are available at the client. This state corresponds to the ZOMBIE state in the GridWay system. drmaa_wait() and drmaa_synchronize() calls on the job will return immediately. Also rusage information is available.
| #define DRMAA_PS_FAILED 0x40 |
FAILED Job state. Job execution has failed, and the "on_failure" policy is to hold it on FAILED state. This state corresponds to the FAILED state in the GridWay system.
| #define DRMAA_PS_QUEUED_ACTIVE 0x10 |
QUEUED-ACTIVE Job state. The job has been successfully submitted and it is pending to be scheduled. This state corresponds to the PENDING state in the GridWay system.
| #define DRMAA_PS_RUNNING 0x20 |
RUNNING Job state. The job has been successfully scheduled and dispatched to a remote host.Please note that once submitted, the job can be in any of the execution states, namely: PROLOG (file stage-in), WRAPPER (execution), EPILOG (file stage-out) or MIGRATING (to another host).
| #define DRMAA_PS_SYSTEM_ON_HOLD 0x11 |
SYSTEM-ON-HOLD Job state. The GridWay system does NOT DEFINE a SYSTEM-ON-HOLD state (currently), and so it will not be never returned by a drmaa_job_ps() call.
| #define DRMAA_PS_SYSTEM_SUSPENDED 0x21 |
SYSTEM-SUSPENDED Job state. The GridWay system does NOT DEFINE a SYSTEM-SUSPENDED state, and so it will not be never returned by a drmaa_job_ps() call.
| #define DRMAA_PS_UNDETERMINED 0x00 |
UNDETERMINED Job state. An UNDETERMINED state can either be obtained due to a communication error with the GridWay daemon, or because the job has not been initialized yet.
| #define DRMAA_PS_USER_ON_HOLD 0x12 |
USER-ON-HOLD Job state. The job has been held by the user. This state corresponds to the HOLD state in the GridWay system.
| #define DRMAA_PS_USER_SUSPENDED 0x22 |
USER-SUSPENDED Job state. The job has been successfully stopped. This state corresponds to the STOPPED state in the GridWay system. Once stopped, restart files (if provided by the job) have been tranferred to the client.
| #define DRMAA_PS_USER_SYSTEM_ON_HOLD 0x13 |
USER-SYSTEM-ON-HOLD Job state. The GridWay system does NOT DEFINE a USER-SYSTEM-ON-HOLD state, and so it will not be never returned by a drmaa_job_ps() call.
| #define DRMAA_PS_USER_SYSTEM_SUSPENDED 0x23 |
USER-SYSTEM-SUSPENDED Job state. The GridWay system does NOT DEFINE a USER-SYSTEM-SUSPENDED state, and so it will not be never returned by a drmaa_job_ps() call.
| #define DRMAA_TIMEOUT_NO_WAIT 0 |
Pre-defined timeout to be used with drmaa_wait() and drmaa_synchronize() function calls. DRMAA_TIMEOUT_NO_WAIT, can be used to specify no timeout at all.
| #define DRMAA_TIMEOUT_WAIT_FOREVER -1 |
Pre-defined timeout to be used with drmaa_wait() and drmaa_synchronize() function calls. DRMAA_TIMEOUT_WAIT_FOREVER, can be used to specify an undetermined amount of time.