v
SYSCPUS - returns in a stem variable information about all CPUs that are
on-line.
v
SYSDSN - returns OK if the specified data set exists; otherwise, it returns an
appropriate error message.
v
SYSVAR - uses specific argument values to return information about the user,
terminal, language, exec, system, and console session.
Following are brief explanations about how to use the TSO/E external functions. For
complete information, see
Using the GETMSG Function
The GETMSG function retrieves a system message issued during an extended
MCS console session. The retrieved message can be either a response to a
command or any other system message, depending on the message type you
specify.
The message text and associated information are stored in variables, which can be
displayed or used within the REXX exec. The function call is replaced by a function
code that indicates whether the call was successful. See
for more information about the syntax, function codes, and variables for
GETMSG. You must have CONSOLE command authority to use the GETMSG
function. Before you issue GETMSG, you must:
v
Use the TSO/E CONSPROF command to specify the types of messages that are
not to be displayed at the terminal. The CONSPROF command can be used
before you activate a console session and during a console session if values
need to be changed.
v
Use the TSO/E CONSOLE command to activate an extended MCS console
session.
The GETMSG function can be used only in REXX execs that run in the TSO/E
address space.
Using the LISTDSI Function
You can use the LISTDSI (list data set information) function to retrieve detailed
information about a data set’s attributes. The attribute information is stored in
variables, which can be displayed or used within instructions. The function call is
replaced by a function code that indicates whether the call was successful.
The LISTDSI function can be used only in REXX execs that run in the TSO/E
address space.
To retrieve the attribute information, include the data set name within parentheses
after LISTDSI. When you specify a fully-qualified data set name, be sure to enclose
it in two sets of quotation marks as follows; one set to define it as a literal string to
REXX and the other to indicate a fully-qualified data set to TSO/E.
x = LISTDSI("'proj5.rexx.exec'")
/* x is set to a function code */
or
x = LISTDSI('proj5.rexx.exec'') /* x is set to a function code */
When you specify a data set name that begins with your prefix (usually your user
ID), you can use one set of quotation marks to define it as a literal string or no
quotation marks. TSO/E adds your prefix to the data set name whether or not it is
enclosed within a set of quotation marks.
TSO/E External Functions
120
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: ......