Note:
To prevent the language processor from searching the data stack, you can
issue the PARSE EXTERNAL instruction instead of PULL. PARSE
EXTERNAL gets input directly from the terminal and bypasses the data
stack.
v
Responses to commands
A TSO/E interactive command (such as LISTDS, TRANSMIT, and ALLOCATE)
can prompt a terminal user for information. Similarly, user responses can be put
on the data stack by an exec for the command’s use.
v
Commands to be issued after the exec ends
When an exec ends, all elements remaining on the data stack are processed
before the READY mode message is displayed. These remaining elements are
treated as TSO/E commands to be issued. If the element is not a TSO/E
command (or an implicit exec or CLIST to be run), you see the message:
COMMAND command_name NOT FOUND
v
Information the EXECIO command reads from and writes to data sets when
performing I/O.
For information about the EXECIO command and how it uses the data stack, see
“Using EXECIO to Process Information to and from Data Sets” on page 154.
Using the Data Stack
The data stack has some unique characteristics, such as:
v
It can contain a virtually unlimited number of data items of virtually unlimited size.
v
It can contain commands to be issued after the exec ends.
v
It can pass information between REXX execs and other types of programs in a
TSO/E or non-TSO/E address space.
Because of the data stack’s unique characteristics, you can use the data stack
specifically to:
v
Store a large number of data items for a single exec’s use.
v
Pass a large number of arguments or an unknown number of arguments
between a routine (subroutine or function) and the main exec.
v
Pass responses to an interactive command that can run after the exec ends.
v
Store data items from an input data set, which were read by the EXECIO
command. For information about the EXECIO command, see “Using EXECIO to
Process Information to and from Data Sets” on page 154.
v
Share information between an exec and any program running in MVS. For more
information about running REXX execs in MVS, see “Chapter 13. Using REXX in
TSO/E and Other MVS Address Spaces” on page 171.
v
Execute subcommands of a TSO/E command issued from a REXX exec.
Passing Information Between a Routine and the Main Exec
You can use the data stack to pass information from an exec to an external routine
without using arguments. The exec pushes or queues the information on the stack
and the routine pulls it off and uses it as in the following example.
Processing of the Data Stack
140
z/OS V1R1.0 TSO/E REXX User’s Guide
Summary of Contents for TSO/E REXX
Page 1: ...z OS TSO E REXX User s Guide SA22 7791 00 ...
Page 2: ......
Page 3: ...z OS TSO E REXX User s Guide SA22 7791 00 ...
Page 10: ...viii z OS V1R1 0 TSO E REXX User s Guide ...
Page 12: ...x z OS V1R1 0 TSO E REXX User s Guide ...
Page 14: ...xii z OS V1R1 0 TSO E REXX User s Guide ...
Page 18: ...xvi z OS V1R1 0 TSO E REXX User s Guide ...
Page 20: ...2 z OS V1R1 0 TSO E REXX User s Guide ...
Page 58: ...Tracing Expressions with the TRACE Instruction 40 z OS V1R1 0 TSO E REXX User s Guide ...
Page 78: ...60 z OS V1R1 0 TSO E REXX User s Guide ...
Page 86: ...Built In Functions 68 z OS V1R1 0 TSO E REXX User s Guide ...
Page 128: ...Issuing Other Types of Commands from an Exec 110 z OS V1R1 0 TSO E REXX User s Guide ...
Page 136: ...Debugging Execs 118 z OS V1R1 0 TSO E REXX User s Guide ...
Page 170: ...Protecting Elements in the Data Stack 152 z OS V1R1 0 TSO E REXX User s Guide ...
Page 201: ...Part 3 Appendixes Copyright IBM Corp 1988 2001 183 ...
Page 202: ...184 z OS V1R1 0 TSO E REXX User s Guide ...
Page 222: ...Using Variables 204 z OS V1R1 0 TSO E REXX User s Guide ...
Page 226: ...208 z OS V1R1 0 TSO E REXX User s Guide ...
Page 238: ...220 z OS V1R1 0 TSO E REXX User s Guide ...
Page 241: ......