Scheduling and Un-Scheduling Jobs

Before talking about how to ``schedule'' or un-schedule'' a job lets talk a step back and talk about what ``scheduling'' and ``un-scheduling'' are. Scheduling a job is the process of adding a job to a queue so that it may at some future time start running. Think of it like this, you living in the early 30's, depression area, have no work, and have thread-bare clothes. So, you, along with almost everyone else, is waiting in a queue for work. You wait and wait and wait until finally you get to the front of the queue and then can begin working. It's just like that for the job, but of course it'd have far better looking clothes on. Un-scheduling is the process of removing this job from the queue. Now that we have that out of the way, we can talk about how GAT facilitates these processes.

First scheduling. During the process of creating a Job it is automatically scheduled. That was easy. So, in particular, one shouldn't play about creating jobs as when on is creating it's ``live'' and actually using resources on some real computer. To un-schedule the job one simply calls the function UnSchedule on the Job instance. Nice how the responsibility for scheduling and un-scheduling is spread across two classes. This is just a little quirk of GAT that I'm sure will be ironed out in time.