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

Usage Notes
Examples
PIPE CONSOLE
An exposed message is a message that fits all of the following criteria:
v Passed to DSIEX02A
v Copied or routed to satisfy ASSIGN stage actions
v Matched for &WAIT or TRAP conditions
v Matched for actions specified in the NetView automation table
v Passed to DSIEX16
v Logged to the network log, hardcopy log, or system log.
Note: Display of messages is subject to the DISPLAY setting of the DEFAULTS
and OVERRIDE stages. Messages displayed this way are subject to NLS
translation.
XDUMP
Produces the same output as DUMP. Also included are the AIFR body and
other information that accompanies some messages. For example, MVS
messages include MDB data as indicated in mapping DSIAIFRO. See
“Example: Displaying Messages in Dump Format” on page 46.
Reference: See the IBM Tivoli NetView for z/OS Programming: Assembler for
mapping for DSIIFR for AIFR information.
Attention: DUMP and XDUMP are not intended as a programming interface,
because formats might change and additional data might be included in the
future. Use DUMP and XDUMP only for problem determination.
v CONSOLE cannot be the first stage.
v The CONSOLE stage presents copies of the messages that come to it in the same
way as other NetView commands. Thus, when CONSOLE is found on an inner
pipeline (a pipeline running as a result of a PIPE command on a NETVIEW
stage on another outer pipeline), the output of CONSOLE is trapped by the outer
pipeline and is passed to the next stage in that outer pipeline.
v The ONLY option can be used to avoid filling the log with extraneous messages.
v A PIPE command submitted to the NetView program from the MVS
environment can have a stage and response token (CART) value associated with
the command. (You can do this from TSO command procedures.) In this case,
output from the CONSOLE stage carries the CART for accurate correlation.
v When using multiple CONSOLE stages, the order of displayed messages
(whether they are single-line messages or MLWTOs) is unpredictable. To control
the order, use the COLLECT stage preceding the CONSOLE stage to collect
pipeline messages into an MLWTO.
v If you use the CONSOLE DELETE stage subsequent to a CONSOLE or a
CONSOLE ONLY stage, some messages can be deleted by the CONSOLE
DELETE stage before they are displayed.
Example: Displaying Messages on a Console
To issue a NetView LIST command, discard messages containing the phrase NOT
ACTIVE in positions 55 through 64, and display the resulting messages (after
clearing the screen), enter:
Chapter 2. Pipeline Stages and Syntax 45