Job Management

As the culmination of your triple PhD's in Computer Science, Neuroscience, and Cognitive Science, you've cobbled together a wee-bit of code which you've taken to affectionally calling GAL 9000. It's a accurate simulation of a fully functioning human brain modeling all the brain's structure, soup to nuts, from neurotransmitter to encephalon. The only problem is, due to the recent round of funding cuts, all you have to run this code-art upon is your limp gimp VIC-20 which you ferreted out from the piles of rotting munchichi's stashed in the attic of your childhood home. With only 3.5K of RAM available to run your code-art on, not even the likes of God could optimize memory usage enough to get you're ``little me'' up and running on the VIC. What is to be done?

Though you've not really been paying attention to all this ``grid'' hype as of late, one point has caught your attention - the grid's promise to allow the vast ever growing sea of the net, populated with hardware resources the likes of which you've only dreamt, to stand at your beckon command. Maybe this is where you should set your child free? The question is how?

The answer, GAT. GAT allows for an application programmer to start, stop, checkpoint, migrate, ...computer processes across this endless sea of the net, and it allows the application programmer to do so, in typical GAT style, effortlessly. All of this functionality is squeezed tight within the job management package, who's study we now embark.

Quite generally, an application programmer need only describe, in a remarkably simple manner, the software they wish to run and the hardware on which they wish to run it, then the prestidigitator GAT handles the rest. So, Pygmalion you need not pray to Aphrodite to free you Galatea from the base stone of a VIC-20, GAT will do just fine.