IBM System 360 User Manual page 76

The first JCL statement in the data set is usually a JOB statement.
The jobname in the JOB statement can be up to eight characters in length
and consists of your user identification followed by one or more letters
or numbers. For example SMITH23 or JONESXYZ.
If the jobnarne consists of only your user identification, the system
will prompt you for a single character to complete the jobnarre. When
you submit the job with the SUBMIT command this allows you to change
jobnames without re-edi ting the data. For example, you may submit the
same job several times, and supply a different character for the job
name each time you are prompted.
If the jobname does not begin with your user identification, you can
su.t>mit it with the SUBMIT command and request its status with the STATUS
command, but you cannot refer to it with the CANCEL or OUTPUT command.
If the first statement of your data set is not a JOB statement, the
system generates the following JOB statement when you submit it with the
SUBMIT command.
//userid JOB
/ /
/ /
/ /
,
GENERATED JOB STATEMENT
userid,
MSGLEVEL=(l,l) ,
NOTIFY=userid
You lII1ill be prompted for a character to complete the jobname.
When you enter the SUBMIT command you must give the name of the data
set (or data sets) that contains the background jobs. You can also
specify the NONOTIFY operand to specify that you do not want to be
notified when a background job with a generated JOB statement
terminates.
Figure 13 shows how
to
create and submit a background job. The data
set type on the EDIT command should be CNTL for best ,system perf or-mance.
Submitted data sets must have a fixed record length of 80 bytes and must
not contain lowercase characters.
You may include more than one job in one data set. You can omit the
JOB statement for the first job, but all jobs after the first must have
their own JOB statement. Although you submit all jobs in the data set
with one
3UBMI'!'
command, you can subsequently refer to each job with
separate STATUS, CANCEL, and OUTPUT commands.
If an error occurs while the jobs are being processed by TSO before
actually being submitted, further processing will be terminated. No
other input specified by the SUBMIT command will be processed. When you
submit more than one job with a single command, and TSO finds an error
while processing the first job, the second job is not processed. An
error that occurs in the second job does not affect the first. Any jobs
processed prior to the error are submitted for execution; jobs that were
not processed because of the error cannot be submitted.
74 TSO Terminal User's Guide (Release 21.7)