Service
Non-TSO/E
Address Space
TSO/E Address
Space
v
SETLANG — controls the language in which REXX messages are
displayed
X
X
v
STORAGE — retrieves and optionally changes the value in a storage
address
X
X
v
SYSCPUS — returns information about CPUs that are online
X
X
v
SYSDSN — returns information about the availability of a data set
X
v
SYSVAR — returns information about the user, the terminal, the exec,
and the system
X
Interaction with CLISTs
— Execs and CLISTs can call each other and
pass information back and forth. For more information, see “Running an
Exec from a CLIST” on page 175.
X
ISPF and ISPF/PDF services
— An exec that is invoked from ISPF can
use that dialog manager’s services.
X
Running Execs in a TSO/E Address Space
Earlier sections in this book described how to run an exec in TSO/E explicitly and
implicitly in the
foreground
. When you run an exec in the foreground, you do not
have use of your terminal until the exec completes. Another way to run an exec is
in the
background
, which allows you full use of your terminal while the exec runs.
Running an Exec in the Foreground
Interactive execs and ones written that involve user applications are generally run in
the foreground. You can invoke an exec in the foreground in the following ways:
v
Explicitly with the EXEC command. For more information, see “Running an Exec
Explicitly” on page 16.
v
Implicitly by member name if the PDS containing the exec was previously
allocated to SYSPROC or SYSEXEC. (Your installation might have a different
name for the system file that contains execs. For the purposes of this book, it is
called SYSEXEC.) For more information, see “Running an Exec Implicitly” on
page 17 and “Appendix A. Allocating Data Sets” on page 185.
v
From another exec as an external function or subroutine, as long as both execs
are in the same PDS or the PDSs containing the execs are allocated to a system
file, for example SYSPROC or SYSEXEC. For more information about external
functions and subroutines, see “Chapter 6. Writing Subroutines and Functions” on
page 69.
v
From a CLIST or other program. For more information, see “Running an Exec
from a CLIST” on page 175.
Services Available to REXX Execs
Chapter 13. Using REXX in TSO/E and Other MVS Address Spaces
173
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: ......