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

Stage 7 writes output to stream 1, "Task Task’s ".
Stage 7 reads input from stream 3, "type ID ".
Stage 7 writes output to stream 1, "type ID ".
Terminating stage number 7, "FANIN ".
The first lines show the FANIN input and output streams and connected stages.
Each stage is shown along with its stage number within the pipeline.
Next, the first few characters of each message flowing on the data streams being
debugged are shown. Each line indicates the stage number and whether the
message is flowing on an input or output data stream. The data stream number is
also included.
Note: In this example with only one DEBUG option in the pipeline, it is obvious
that the FANIN stage is being traced without having to explicitly specify
“Stage 7”. However, the stage number is important when multiple DEBUG
options are coded in a single pipeline. The stage number, in that case,
indicates the stage for which activity is being traced.
Finally, the last message shows that the stage termination conditions have been
met and that FANIN is terminating. For information on stage termination
conditions, see the individual stage descriptions in Chapter 2, “Pipeline Stages and
Syntax,” on page 19.
The following coding rules apply to DEBUG as a stage option.
v DEBUG can be added to any pipe stage after the label and immediately before
the stage.
v The DEBUG option must be enclosed in parenthesis.
v If you need to include DEBUG on the first stage in the pipeline and you have
not specified pipeline options, include an empty pipeline option string before
DEBUG. For example, the following command cannot be used:
PIPE (DEBUG) NETV LIST X|...
However, either of the following commands works:
PIPE () (DEBUG) NETV LIST X|...
PIPE | (DEBUG) NETV LIST X|...
v For stages modifying the action of other stages, for example NOT and CASEI,
include DEBUG before the modifier. For example, use the following command:
PIPE ...|(DEBUG) CASEI LOCATE /X/|...
But, not this:
PIPE ...|CASEI (DEBUG) LOCATE /X/|...
DEBUG Pipeline Option
DEBUG can also be included in the pipeline options. When included as a pipeline
option, DEBUG affects all stages within the pipeline.
Data Stream Tracing: Coding DEBUG 1 in the pipeline options is the same as
coding DEBUG on each pipeline stage. For example:
PIPE (NAME SAMP DEBUG 1)
| < MYFILE
| STRIP TRAILING / /
| JOINCONT TRAILING /$/
| CONSOLE
Is the same as:
Debugging NetView Pipelines
Chapter 8. Debugging NetView Pipelines 349