Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Coding responses to prompts - the DATA PROMPT-ENDDATA sequence z/OS TSO/E CLISTs SA32-0978-00 |
|
If you execute a CLIST in the background, a user cannot respond to prompts from the CLIST. To avoid this problem, use the DATA PROMPT-ENDDATA sequence. The DATA PROMPT-ENDDATA sequence lets you designate responses to prompts by TSO/E commands or subcommands. To use the DATA PROMPT-ENDDATA sequence, code:
If the sequence is not immediately preceded by a TSO/E command or subcommand that prompts, an error occurs (error code 968 appears in control variable &LASTCC). You can ignore the error condition if a command or subcommand that might prompt, does not prompt. The responses in the DATA PROMPT-ENDDATA sequence must appear exactly as if a user entered the response. Each DATA PROMPT-ENDDATA sequence can respond only to prompts issued by the immediately preceding command or subcommand. However, you can include multiple responses to satisfy multiple prompts. Excess responses can result in an error message and termination of the CLIST if an error routine is not present. To stop TSO/E commands from prompting after a DATA PROMPT-ENDDATA
sequence, code a null line after ENDDATA. To code a null line, first
set a variable equal to null:
Then place that variable on the line after ENDDATA:
Some TSO/E commands prompt for input when you code certain operands.
For example, the LINK command invokes the linkage editor. When you
substitute an asterisk (*) for the data set name, TSO/E prompts for
control statements. If you include such a LINK command in a CLIST
that might run in the background, place the control statements within
a DATA PROMPT-ENDDATA sequence. The following CLIST, when run in
the background, link-edits the member X, which resides in the
file DD1:
There are additional considerations for using the DATA PROMPT-ENDDATA
sequence:
|
Copyright IBM Corporation 1990, 2014
|