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

PIPE NETVIEW
messages that are issued in the immediate environment. Results are messages or
other actions that are caused by the command, but not immediately or not for
the issuing environment.
For example, the MSG command causes two messages, one output and one
result. The DSI039I MSG FROM ... is a result. It is not trapped in the pipeline,
even if sent to the same operator where the MSG command was issued. The
DSI001I MESSAGE SENT TO... message is output and is trapped by the CORR=CMD
parameter to the DSIMQS invocation pipeline for further processing by
subsequent stages. Also, read about the CORRWAIT and PERSIST stages; see
“PIPE CORRWAIT ” on page 54 and “PIPE PERSIST” on page 179.
v The following commands are among those NetView commands supported:
– User-written commands that use the CORR keyword on DSIPUSH, DSIFIND,
or DSIMQS assembler macros. See the IBM Tivoli NetView for
z/OS Programming: Assembler for more information about these macros.
– MVS system commands issued from the NetView program, if extended
multiple console support (EMCS) consoles are being used.
For more information about EMCS consoles, see the MVSPARM statement in
the IBM Tivoli NetView for z/OS Administration Reference.
When using MVS to address commands to another subsystem (such as JES2),
correlation depends upon that subsystem's proper use of the MVS CART
message correlators and upon that subsystem's proper routing of response
messages. If messages from another subsystem do not appear to be properly
processed by your pipelines, contact the support representative for the
subsystem being addressed to see if CART support is available on the version
of the subsystem you are using.
– ENDTASK. ENDTASK commands support correlation and can be used in
cross-domain pipes for commands between NetView V3R1, or later, programs.
ENDTASK commands to and from NetView programs before V3R1 can be
executed in a NetView PIPE, but the response does not flow back through the
PIPE.
– RUNCMD. See IBM Tivoli NetView for z/OS Programming: REXX and the
NetView Command List Language for more information about using RUNCMD.
– Other NetView commands that are correlated (those with displayable output).
See PIPE HOLE for information on determining if a command has correlated
output.
v If you have your own commands (user-written) that produce messages
asynchronously, you can modify them so that they are supported by NetView
Pipelines. There are two ways to do this:
– Correlation method.
If your command solicits data from a DST or other NetView task by sending
a command to that task by the DSIMQS macro, you can add an option. This
option causes a correlator to be attached to the command that is sent. When
the command runs, it can return correlated messages to the originating task
by issuing DSIPSS TYPE=OUTPUT.
– Long running command (LRC) method.
You can use the long running command support provided by the NetView
program to change asynchronous messages into synchronous ones. Use
DSIPUSH to make your command an LRC. However your data is returned to
the originating task, it must be made available to your resume routine.
Usually, this is done by causing a command to run at the originating task
which can use DSIFIND to access rstorage that is accessible to the resume
Chapter 2. Pipeline Stages and Syntax 169