[ogsa-bes-wg] CIM JobState enumeration

[Christopher Smith]

Hi all,

First off ... apologies that I'll have to miss the call this morning. I'm
still at O'Hare waiting for my 12:30am flight back to SF ... ETA at home at
3:30 or 4am. :-P

I've looked into the operational states that the CIM model enumerates for
BatchJob. They are actually inherited from the ConcreteJob object from the
core model. 

Covers the basic states for the execution of the activity itself, but
(probably as expected) does not cover the entire state + sub-state model
that we have for an activity. Nice in that they do cover transitional states
as well. Really just missing the file transfer sub-states.

The states themselves:

          "JobState is an integer enumeration that indicates the "
          "operational state of a Job. It can also indicate "
          "transitions between these states, for example, 'Shutting "
          "Down' and 'Starting'. Following is a brief description of "
          "the states: \n"
          "New (2) indicates that the job has never been started. \n"
          "Starting (3) indicates that the job is moving from the "
          "'New', 'Suspended', or 'Service' states into the 'Running' "
          "state. \n"
          "Running (4) indicates that the Job is running. \n"
          "Suspended (5) indicates that the Job is stopped, but may be "
          "restarted in a seamless manner. \n"
          "Shutting Down (6) indicates the job is moving to a "
          "'Completed', 'Terminated', or 'Killed' state. \n"
          "Completed (7) indicates that the job has completed "
          "normally. \n"
          "Terminated (8) indicates that the job has been stopped by a "
          "'Terminate' state change request. The job and all its "
          "underlying processes are ended and may be restarted (this "
          "is job-specific) only as a new job. \n"
          "Killed (9) indicates that the job has been stopped by a "
          "'Kill' state change request. Underlying processes may have "
          "been left running and cleanup may be required to free up "
          "resources. \n"
          "Exception (10) indicates that the Job is in an abnormal "
          "state that may be indicative of an error condition. Actual "
          "status may be surfaced though job-specific objects. \n"
          "Service (11) indicates that the Job is in a vendor-specific "
          "state that supports problem discovery and/or resolution."),


-- Chris