EXEC command operands

data_set_name(member_name)

specifies the unqualified name of a partitioned data set whose type is CLIST or exec. The data_set_name is the library name such as the name SESSION in the data set PREFIX.SESSION.CLIST.(member_name) is the name of the CLIST or exec. For example, to execute prefix.session.clist(first), specify:

exec session (first)

(member_name)

specifies a member of a partitioned data set whose type is CLIST or exec. (member_name) is the name of the CLIST or exec. For example, to execute an exec named prefix.exec(two), specify:

exec (two) exec

data_set_name

specifies the unqualified name of a sequential data set whose type is CLIST or exec. Data_set_name is the name of the CLIST or exec. For example, to execute a CLIST named prefix.test.clist, specify:

exec test.clist

'data_set_name'

specifies the fully-qualified name of a sequential data set. For example, to execute an exec named project.num.one, specify:

exec 'project.num.one' exec

If the data set is not a sequential, but a partitioned one, a member TEMPNAME is assumed. If such member does not exist, the system will notify you, otherwise it will be executed.

'data_set_name(member_name)'

specifies the fully-qualified name of a partitioned data set. (member_name) is the name of the CLIST or exec. For example, to execute a CLIST named PROJECT.SPECIAL.$1993(MARCH), specify:

exec 'PROJECT.SPECIAL.$1993(MARCH)'

A CLIST or REXX exec data set may contain line numbers according to the following format:

• Variable blocked — First 8 characters in each record. If the data in columns 1-8 is not numeric, the CLIST or exec treats it as data.
• Fixed blocked — Last 8 characters in each record

You are suggested to use variable blocked records, although you can also use fixed blocked here.

p_value

For use with CLISTs only. A p_value is the actual value a user specifies for each positional parameter on the PROC statement. Lowercase values are changed to uppercase.

The user must specify a p_value for each positional parameter in the same sequence as each appears on the PROC statement (for example, p_value₁ p_value₂ … p_value_n).

If a user does not specify a p_value for a positional parameter, the CLIST prompts for the value. See Considerations for passing quotation marks for more information.

argument

For use with execs only. Specifies a parameter passed to an exec.

k_word

For use with CLISTs only. k_word is the actual keyword a user specifies. It can be an abbreviation if it is different from all other k_word parameters in the EXEC command.

The specification of k_word must follow all p_value specifications; but k_words may be specified in any order.

k_value

A value associated with a k_word.

'k_value'

k_value is a quoted string. Lowercase values are changed to uppercase.

Specification on the PROC statement: keyword()

• If the user specifies k_word without a k_value, the CLIST prompts for the value.
• If the user does not specify k_word, the associated keyword has a null value.

Specification on the PROC statement: keyword(default value)

• If the user specifies k_word without a k_value, the CLIST prompts for the value.
• If the user does not specify k_word, the CLIST uses the default value.
• If the user specifies k_word with a k_value, the CLIST uses k_value.

See Considerations for passing quotation marks for more information.

NOLIST | LIST

specifies whether commands and subcommands are to be listed at the terminal as they are executed.

NOLIST

specifies commands and subcommands are not to be listed. The system assumes NOLIST for implicit and explicit EXEC commands. NOLIST is the default.

LIST

specifies commands and subcommands are to be listed. This operand is valid only for the explicit form of EXEC.

NOPROMPT | PROMPT

NOPROMPT

specifies no prompting during the execution of a CLIST or REXX exec. NOPROMPT is the default.

No prompting is allowed during the execution of a program if the NOPROMPT keyword operand of PROFILE has been specified, even if the PROMPT option of EXEC has been specified.

PROMPT

specifies prompting to the terminal is allowed during the execution of a CLIST or REXX exec. The PROMPT keyword implies LIST, unless NOLIST has been explicitly specified. Therefore, all commands and subcommands are listed at the terminal as they are executed. This operand is valid only for the explicit form of EXEC.

The PROMPT keyword is not propagated to nested EXEC commands. If you want to be prompted during execution of the program it invokes, PROMPT must be specified on a nested EXEC command.

The following is a list of options resulting from specific keyword entries:

Keyword specified	Resulting options
PROMPT   NOPROMPT   LIST   NOLIST   PROMPT LIST PROMPT NOLIST NOPROMPT LIST NOPROMPT NOLIST No keywords	PROMPT LIST NOPROMPT NOLIST LIST NOPROMPT NOLIST NOPROMPT PROMPT LIST PROMPT NOLIST NOPROMPT LIST NOPROMPT NOLIST NOPROMPT NOLIST

CLIST | EXEC

specifies whether a CLIST or an exec is to be run. To fully qualify the data set name, the EXEC command adds the suffix CLIST or EXEC to the data set name. For more information about these operands, including what happens when you omit the parameter, see Using the explicit form of the EXEC command.

CLIST

specifies that a CLIST is to be run.

EXEC

specifies that an exec is to be run.

%member_name

specifies the name of a CLIST or exec. If the percent sign (%) is entered, TSO/E searches its procedure libraries for a CLIST or exec only. It does not search for a command. For example, to execute an exec named prefix.myrexx.exec(new) that is allocated to a procedure library, specify:

%new

PROC 3 INPUT OUTPUT LIST LINES( )
allocate dataset(&input) file(indata) old
allocate dataset(&output) block(100) space(300,100)
allocate dataset(&list) file(print)
call proc2 '&lines'
end

The PROC statement indicates that the three symbolic values, &INPUT,; &OUTPUT and &LIST, are positional (required) and that the symbolic value &LINES is a keyword (optional).

anzal alpha beta comment lines(20)