Chapter Contents

Previous

Next

exec (TSO)

Execute a CLIST or EXEC under TSO

ABBREVIATION

exe{c}

FORMAT

exec CLIST-NAME | EXEC-NAME ['ARGUMENTS'] [list | nolist] [prompt | noprompt]

DESCRIPTION

The exec command executes a CLIST or a REXX EXEC specified by the CLIST-NAME or EXEC-NAME argument. CLIST-NAME or EXEC-NAME is the name of a member in a partitioned data set containing command procedures (CLISTs) or a REXX EXEC.

The data set can contain either CLIST or REXX statements and control variables as well as SAS/C Debugger commands. Debugger commands are passed back to the debugger and performed. TSO commands cannot be executed directly from a CLIST. However, they can be executed using the system debugger command.

If you execute a REXX EXEC from the debugger, you can issue either TSO commands or debugger commands with the REXX ADDRESS. ADDRESS CDEBUG is used to issue debugger commands and ADDRESS TSO is used to issue TSO commands.

You can specify values for ARGUMENTS to be passed to your CLIST or EXEC, and you can specify the list, nolist, prompt, or noprompt keyword. See the IBM publication OS/390 V2R9.0 TSO/E Command Reference SC28-1969 for a discussion of the TSO EXEC command and the list, nolist, prompt, and noprompt keywords.

The data set name must follow TSO naming conventions for data sets containing CLISTs or EXECs in a TSO EXEC command. According to these conventions, if the final qualifier of the CLIST is not "clist," the fully qualified data set name must be specified inside single quotation marks. Line numbers (if they exist) in the data set must follow these rules:

fixed block data set

In each record, the line number is the last eight characters.

variable blocked data set

In each record, the line number is the first eight characters.

See the IBM publication TSO/E Command Reference SC28-1969 for a discussion of CLISTs. See the IBM publication OS/390 V2R9.0 TSO/E REXX User's Guide SC28-1974 for information about REXX EXECs.

You cannot use another debugger command on the same line following exec. If another debugger command occurs on the same line after exec, the debugger ignores it with a warning.

Similarly, no other debugger command can be issued on the same line as exec when it is used as an argument to on (but you can use another command following exec on a separate line). Any command following exec on the same line is ignored.

If a CLIST or EXEC contains a debugger go, step, continue, exit, abort, or resume command, the command is executed and the CLIST or EXEC is ended. Any debugger commands in the CLIST or EXEC following one of these commands are not performed. In an EXEC, any commands after one of these commands are rejected with a return code of -10.

ADDITIONAL DISCUSSION AND EXAMPLES

See Return Codes Set by Debugger Commands.

SYSTEM DEPENDENCIES

The exec command followed by a CLIST argument is only valid for TSO. See the CMS version of exec.

COMMAND CAN BE ISSUED FROM

PROFILE	yes
configuration file	no
Source window prefix	none

SCOPE

The exec command is not affected by changes in scope.

RETURN CODES SET

	Successful: code set by the CLIST called
	Unsuccessful: parsing error, - 1; otherwise, execopn() code

Chapter Contents

Previous

Next

Top of Page

Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.