Spool
The holding area where a job's output waits until someone reads it, prints it or removes it.
Also written JES spool, output queue
Why it matters. A job has no screen of its own. Its results are in the spool, and that's where you read them.
See it
Follow HELLO through the queue
Submit it, and watch JES2 take it from there.
- 1Taken in
- 2Waits its turn
- 3Runs
- 4Ends, output kept
READY SUBMIT 'ZBANK.DEV.JCL(HELLO)'
Syntax
SDSF, then O OUTPUT jobname[(jobid)] [PRINT(*)]
- jobname
- The job whose output to get.
- PRINT(*)
- Show the output at your terminal. PRINT(dsname) copies it to a dataset.
- KEEP / DELETE
- Keep the output on the spool afterwards, or remove it.
- HOLD / NOHOLD
- Hold the output, or let it print normally.
Try it SDSF O
- 1
Open SDSF, the screen where you watch jobs and send operator commands.
SDSF - 2
See which jobs have output waiting in the spool.
COMMAND INPUT ===> O - 3
Read the job log, the part called JESMSGLG. Beside its row, in the NP column, use the line command that selects it.
NP S
Remember
- A job's printed output goes to the spool, not to your screen.
- It stays there until someone reads it, prints it or purges it.
- SDSF and the TSO OUTPUT command both read the spool.
The usual mistake
The output disappears when the job ends.
The spool holds it. It stays until someone reads it, prints it or purges it.
Read it in SDSF, and purge it when you're done.
On real z/OS
MF/OS shows the NP line command as a typed line and prints the log as text. Real SDSF is full screen: you move the cursor to the row and type S. The TSO OUTPUT command works on the whole job (and only on jobs named with your user ID plus up to seven characters), so SDSF is the usual way to read one part. MF/OS doesn't model JES2 spool volumes, checkpoint or output classes beyond the basics.
Where can I practise Spool?
Right here, at ZedBank. You take a junior job at a simulated bank and use Spool in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- SDSFThe tool for looking at what jobs are running, what has finished, and what output they produced.
- SYSOUTOutput sent to the spool rather than to a dataset, where you can read it after the job finishes.
- JES2The job entry subsystem: the part of z/OS that queues jobs, decides when they run, and collects their output.
- JobA unit of batch work submitted to the system, made up of one or more steps that run in order.