SUBMIT command operands

(data_set) | *

(data_set)

specifies one or more data set names or names of members of partitioned data sets that define an input stream (JCL plus data). If you specify more than one data set name, separate them with delimiters, and enclose them in parentheses.

*

An asterisk (*) specifies that the job stream is to be obtained from the current source of input (for example, the terminal or currently executing CLIST). TSO/E commands can be entered directly without creating and editing a data set.

Note: All characters in the job stream are converted to uppercase before being processed.

This positional operand and the data_set positional operand are mutually exclusive. Either of both operands is required.

The SUBMIT * function described here is not available in EDIT mode. Job stream input received directly from the terminal or any other source will not be saved after the job is submitted. The SUBMIT * subcommand of EDIT continues to select the current data set as the input job stream. See the SUBMIT subcommand of EDIT for more information.

If the submitted job contains a job statement, the SUBMIT operands that generate job statements are ignored. The SUBMIT operands do not override the job statement.

Note: When TSO/E processes a job in a CLIST that uses the SUBMIT * command, statements following the DD * statement are left adjusted to column 1, thereby removing leading spaces. (This is unique to CLIST processing only; it is not a batch concern.) Refer to z/OS TSO/E CLISTs, for a procedure that preserves the leading spaces in a CLIST.

PAUSE | END(nn)

PAUSE: specifies that you want to make a decision after the job stream has been read in. This decision is to either continue the SUBMIT * process or terminate. If this operand is omitted, the job stream is processed when the end of the job stream is detected. The default is not to pause when the end of the job stream is reached. If you have not specified PAUSE and you subsequently make an error, the only way the submission can be aborted is with an attention interrupt. This is an optional operand.
Pause is valid only when * (asterisk) is specified for the positional parameter and you are not in EDIT mode.
END(nn): specifies a 1- or 2-character string to indicate the end of the job stream. Only alphabetic, numeric, or the special characters #, $, or @ are valid END characters. If this operand is not specified, a null or blank line indicates the end of the job stream. Specifying this operand allows blank lines to be part of the job stream. To terminate the job stream, the END character(s) must begin in column 1 and be the only data on the input line. The END character string is not considered part of the job stream. END is valid only when * (asterisk) is specified for the positional parameter and when you are not in EDIT mode.

HOLD | NOHOLD

HOLD: specifies SUBMIT is to have job output held for use with the OUTPUT command by defaulting to the held MSGCLASS supplied by the installation manager for the user. Output directed to DD statements is held if SYSOUT=* or HOLD=YES is specified on the DD statement.
NOHOLD: specifies job output is not to be held. NOHOLD is the default.

JOBCHAR(characters) | NOJOBCHAR

JOBCHAR(characters): specifies characters to be appended to the jobname on every JOB statement in the data set being submitted. Use 1 character if you plan to use the STATUS command and your job name is your user ID.
NOJOBCHAR: specifies SUBMIT is to prompt you for jobname characters whenever the job name is the user ID. If prompting is not possible, the jobname character defaults to the letter X. NOJOBCHAR is the default. The user ID is determined by certain rules. See the USER operand for a list of the rules.

PASSWORD | NOPASSWORD

PASSWORD

specifies a PASSWORD operand is to be inserted on the generated JOB statement by SUBMIT, if RACF® is installed. SUBMIT prompts you to enter the password value in print-inhibit mode, if the terminal supports the feature. This operand is not required if a generated JOB statement or RACF is not installed. If RACF is installed, PASSWORD is the default. The password used is:

The password (if executing in the foreground) entered on the LOGON command initiating the foreground session. The current password is used for RACF-defined users. If you have updated your password using the LOGON command, you must enter the PASSWORD operand with the new password on the SUBMIT command.
The password on the LOGON command (if executing in the background) specified in the submitted data set. If a LOGON command is not in the data set, the USER and PASSWORD operands are not to be included on the generated JOB statement.

NOPASSWORD

specifies the PASSWORD and USER operands are not included on the generated JOB statement. If RACF is not installed, NOPASSWORD is the default.

USER(user_id) | NOUSER

USER(user_id)

specifies a USER operand is to be inserted on the generated JOB statement, if RACF is installed. The user ID specified is also used as the jobname for the generated JOB statement. For job name or user ID comparison for NOJOBCHAR processing, see the NOJOBCHAR operand description.

If neither USER nor NOUSER is entered and RACF is installed, USER is the default. The default user ID used is determined by the following rules. The rules are ordered. If the first rule is met, then that user ID is used.

The user ID specified on a LOGON command in the data set being submitted.
The user ID specified on the LOGON command (if executing in the foreground) initiating the foreground session; the user ID specified on the USER operand (if executing in the background, RACF-defined users only) on the JOB statement initiating the background session.
The default user ID SUBMITJB is used.

Note: If a password is not specified, the USER operand is not generated on the job statement. You can specify a password:

On the user's SUBMIT command
On the LOGON command data set being submitted
In the LOGON for the current session, when executing in the foreground, by requesting that the password be stored in the TSB via the LOGON exit

NOUSER

specifies generated JOB statements do not include USER and PASSWORD operands. If USER is not specified and RACF is not installed, NOUSER is the default.

NOTIFY | NONOTIFY

NOTIFY

specifies that you are to be notified when your job terminates in the background, if a JOB statement has not been provided. If you have elected not to receive messages, the message is placed in the broadcast data set. You must then enter LISTBC to receive the message. If a JOB statement is generated, NOTIFY is the default.

When you supply your own JOB statement, use the NOTIFY=user_id keyword on the JOB statement if you want to be notified when the job terminates. SUBMIT ignores the NOTIFY keyword unless it is generating a JOB statement.

If NOTIFY or NONOTIFY is not specified, the default is:

The NOTIFY operand (if executing in the foreground) is inserted on the generated JOB statement.
The NOTIFY operand (if executing in the background) is only inserted on the generated JOB statement for RACF-defined users who have specified the USER operand on the JOB statement initiating the background session.

NONOTIFY

specifies a termination message is not to be issued or placed in the broadcast data set. The NONOTIFY keyword is only recognized when a JOB statement has not been provided with the job that you are processing.