Stoping a Job Instance

GAT gives you the freedom to do whatever you see fit. For example, if you bring a job in to the running state, then decide, for whatever reason, be it logical or whimsy, that this job must be stopped by any means necessary, you can do it with GAT. One might realize, all to late, that one's job has some critical error, and running until the bloody end is all but pointless. So, one would like to preform a little euthanasia and put the job out to pasture. Such a state change would correspond to the state change labeled ``Job is stopped'' in the state diagram detail of figure

Apparent from figure , this ``stopping state change'' can only occur if a GATJob is in the running state. Otherwise, such a ``stopping state change'' is not defined.

To effect such a ``stopping state change'' one makes a call to the function

GATResult GATJob_Stop(GATJob object)

The passed GATJob instance corresponds to the job one wishes to stop. Hence, this passed instance must be in a running state or this function will not complete successfully. This function returns a GATResult, covered in Appendix , which indicates its completion status.