IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

PIPE STEM and PIPE $STEM
PIPE STEM and PIPE $STEM
Syntax
STEM
►►
STEM
$STEM
(0)
(number)
(COMMON)
(TASK)
stemroot
COLLECT
Command Description
The STEM stage can be used anywhere in the pipeline.
Streams
226 Programming: Pipes
FROM 1
FROM frnumber
APPEND
When STEM is the first stage, it reads records from an array of stemmed command
procedure variables. Each record is passed as a single-line message to the pipeline
output stream.
When STEM is not the first stage, it writes each line of each message to a variable
within a stemmed array of command procedure variables and to the output
stream. In addition, an integer is appended to the given variable name (for
example, VARNAMEn). The number represents the position of the message line
being processed. For instance VARNAME1 is the first line, VARNAME2 is the
second line. When all lines are processed, a variable with a zero appended
(VARNAME0) is written to the variable pool, but not to the output stream. This
variable contains the total number of all lines that were processed.
Thus, if VARNAME1,VARNAME2, and VARNAME3 are created containing messages
1, 2, and 3 respectively, VARNAME0 contains the number 3.
The use of the STEM stage is limited to the command procedure environments
(REXX, NetView command list language, and HLL). However, if the (COMMON)
or (TASK) option is used, STEM can be invoked from message automation, by
command originating at the PPT task or an optional task, or by using a labeled
command originating in a command procedure. Use of the STEM stage outside of
these environments results in message DSI290I and termination of the pipeline.
By contrast, the VAR stage reads and writes to uniquely named variables that do
not represent an array.
The $STEM stage is the same as STEM, except that it also reads or writes the
VIEW attribute variables (which start with $) that are associated with the specified
array of stemmed data variables. When $STEM is the first stage, the color and
highlighting specified in the attribute variables are translated to the output
messages. When $STEM is not the first stage, the color and highlighting attributes
specified in the input messages are translated to the attribute variables.
Stream Type Number Supported
Input 1
Output 1
►◄