Using The Data Stack In Tso/E Background And Mvs Batch; Summary Of Tso/E Background And Mvs Batch; Capabilities - IBM TSO/E REXX User Manual

Table of Contents

Advertisement

Running Execs in a Non-TSO/E Address Space

Using the Data Stack in TSO/E Background and MVS Batch

When an exec runs in the TSO/E background or MVS batch, it has the same use of
the data stack as an exec that runs in the TSO/E foreground. The PULL instruction,
however, works differently when the data stack is empty. In the TSO/E foreground,
PULL goes to the terminal for input. In the TSO/E background and MVS batch,
PULL goes to the input stream as defined by ddname SYSTSIN. When SYSTSIN
has no data, the PULL instruction returns a null. If the input stream has no data and
the PULL instruction is in a loop, the exec can result in an infinite loop.

Summary of TSO/E Background and MVS Batch

CAPABILITIES

TSO/E BACKGROUND (IKJEFT01)
Execs run without terminal interaction.
Execs can contain:
v REXX instructions
v Built-in functions
v TSO/E REXX commands
v TSO/E commands
v TSO/E external functions
Execs are invoked through the PARM parameter on the
EXEC statement and through explicit or implicit use of the
EXEC command in the input stream.
Information in the input stream is processed as TSO/E
commands and invocations of execs and CLISTs.
Output sent to a specified output data set or to a
SYSOUT class.
180
z/OS V1R1.0 TSO/E REXX User's Guide
Segment of Output from the JCL Listing
ALLOC. FOR USERIDA MVSBACH
224 ALLOCATED TO OUTDD
954 ALLOCATED TO SYSTSPRT
7E0 ALLOCATED TO SYSEXEC
JES2 ALLOCATED TO SYSTSIN
USERIDA MVSBACH - STEP WAS EXECUTED - COND CODE 0137
USERID.TRACE.OUTPUT
VOL SER NOS= TSO032.
USERID.IRXJCL.OUTPUT
VOL SER NOS= TSO032.
USERID.MYREXX.EXEC
VOL SER NOS= TSO001.
JES2.JOB28359.I0000101
STEP / MVSBACH / START 88167.0826
STEP / MVSBACH / STOP 88167.0826 CPU
JOB / USERIDA / START 88167.0826
JOB / USERIDA / STOP 88167.0826 CPU
KEPT
KEPT
KEPT
SYSIN
0MIN 00.16SEC SRB
0MIN 00.16SEC SRB
MVS BATCH (IRXJCL)
Execs run without terminal interaction.
Execs can contain:
v REXX instructions
v Built-in functions
v TSO/E REXX commands
v The TSO/E external functions, STORAGE and
SETLANG
Execs are invoked through the PARM parameter on the
EXEC statement. The first word on the PARM parameter
is the member name of the PDS to be invoked. Following
words are arguments to be passed.
Information in the input stream is processed as input data
for the exec that is running.
Output sent to a specified output data set or to a
SYSOUT class.
...
...

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents