Submit
Handing JCL to the system to be run, which queues it as a job and gives it a job number.
Also written SUB, job submission
Submitting is how batch work starts. You have JCL in a member; submitting hands it to the job entry subsystem, which validates it, assigns a job number and queues it to run.
The usual method is a single command typed on the command line while editing or browsing the JCL, or against the member in a dataset list. There are other routes. A scheduler submits production work automatically, and a running program or REXX exec can submit a job too.
What comes back immediately is only an acknowledgement and a job number. That number is not a result. The job may not have started, and a submitted job can still be rejected for a JCL error before any step runs.
So submitting is always followed by going to look. Open SDSF, find the job number, and read what happened. That loop of edit, submit, look and fix is the basic rhythm of learning batch, and the looking is where the learning actually is.
Related terms
- 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.