I shouldn't have gone to this session. I was thinking that I could define a MAS complex and then be able to route jobs and printouts effortlessly to my test copy of JES2. It turns out I was mistaken; there are lots of liabilities involved in having a MAS complex, not the least of which is that I could destroy the production JES2.

(A MAS complex is composed of two or more copies of JES2 that share common SPOOL and checkpoint files. Jobs that enter the SPOOL can be executed or printed under the control of any JES2 in the complex. If one JES2 messes up the checkpoint dataset, all systems lose. Multi-Access SPOOL is designed for installations with multiple processors on the machine room floor, not for testing JES2.)