If you don't normally read instructions, congratulations on getting this far. In the interest of all helloWorld examples, here's the bare-bones instructions: python test_submit.py --arch python bootstrap.py #==================================================================== # running a job through the backend without a supervisor #==================================================================== The test_submit.py is a front-end script which builds the jobs to either submit to the supervisor or archive the job to disk; this builds a job archive in binary format, a job.qja file. It can build either a cmdline-type job or an agenda-based job. if you supply a "--arch" flag to test_submit.py, it will write the job to disk as job.qja. if you write the job to disk with the --arch, you can use the bootstrap.py to single-step through the back-end module in this directory, execute.py. The execute.py is the backend code. It can be executed in a test environment by running the bootstrap.py in the same directory. This will serve to emulate the supervisor starting up the subjob and passing the worker the subjob object. If you've created a job.qja and then run bootstrap.py, it should run the job entirely in your dev't environment. "python -m pdb bootstrap.py" will load it all up in a debugger. You'll want to either b(reak) at line 88 in bootstrap.py and then s(tep) into the backend execute.py module, or insert a breakpoint somewhere in the execute.py with: import pdb; pdb.set_trace() Then if you simply run "python bootstrap.py" it will load the job archive, begin to run the backend module, and pause where you set the breakpoint. relevant pdb debugger commands are: * help * b - sets a breakpoint * s - singlestep will descend into functions * r - return from the module or func you're in (handy when you've stepped into somewhere you don't want to be...) * n - like step, but don't descend * q - quit "h b" will show you how to set breakpoints, including conditional bp's. #==================================================================== # running a job through the supervisor #==================================================================== You'll need to copy the helloWorld directory onto a worker, or put it into a directory is the workers "worker_template_path" value. Simplest is to copy it into /pfx/jobtypes/helloWorld. At minimum, the helloWorld directory must contain job.conf and execute.py, but it's OK if it has all the other files present in this directory. No need to restart the worker. If you run "qbhosts -l