Submit
Sends a JCL member to the system, which runs it as a batch job.
Also written SUB, job submission
Why it matters. Most of the bank's work runs as jobs overnight. SUBMIT is how you start one.
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
{SUBMIT | SUB} 'dsname[(member)]' [NOTIFY | NONOTIFY] [HOLD | NOHOLD] [JOBCHAR(characters)]
SUBMIT * (take the JCL from the terminal)- 'dsname(member)'
- The dataset or library member that holds the JCL. Quote it.
- *
- Read the JCL from what you type next. End it with a blank line.
- NOTIFY
- Tell you at the terminal when the job ends.
- HOLD
- Keep the output held in the spool, so OUTPUT can read it.
- JOBCHAR(characters)
- Add characters to the job name, so STATUS and CANCEL can find it.
Try it SUBMIT
- 1
Start the job in the member CUSTCHK of your DEV.JCL library.
SUBMIT 'ZB0001.DEV.JCL(CUSTCHK)' - 2
Now submit a member that is not there: NOPE.
SUBMIT 'ZB0001.DEV.JCL(NOPE)'
Remember
- SUBMIT sends a member. JES2 runs it as a job.
- You get READY back at once. The job runs on its own.
- Keep the job number. You need it for the output.
The usual mistake
SUBMIT 'ZB0001.DEV.JCL'
A library holds many members. SUBMIT has to be told which one to send.
SUBMIT 'ZB0001.DEV.JCL(CUSTCHK)'
On real z/OS
MF/OS accepts a library member only. A plain sequential dataset, SUBMIT *, NOTIFY, HOLD and JOBCHAR are not modelled. MF/OS also runs the job at once and prints $HASP100, $HASP373 and $HASP395 on your screen; on a real system those go to the job log and the console, and SUBMIT itself gives only IKJ56250I and READY.
Where can I practise Submit?
Right here, at ZedBank. You take a junior job at a simulated bank and use Submit in real work, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- JCLJob Control Language: the language used to tell the mainframe what programs to run, in what order, and with what files.
- JobA unit of batch work submitted to the system, made up of one or more steps that run in order.
- JES2The job entry subsystem: the part of z/OS that queues jobs, decides when they run, and collects their output.
- SDSFThe tool for looking at what jobs are running, what has finished, and what output they produced.
- Return codeA number a program leaves behind saying how it went. Zero for clean, higher numbers for warnings and failures.
- TSO commandA command typed at a TSO prompt or on an ISPF command line to ask the system to do something directly.