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

PIPE COLLECT
Examples
42 Programming: Pipes
message. When COLLECT is used without arguments, COLLECT does not
produce output until the previous stage disconnects.
v The message attributes of an output message from COLLECT is derived from
the first message included in that output. For example, if the first message
received by COLLECT had a JOBNAME of TSU00041, then the entire multiline
output bears that same JOBNAME regardless of the origin of the subsequent
lines.
v COLLECT does not alter the message type (HDRMTYPE) of the lines it collects.
This means that the output is not necessarily one of the types J, K, or L as was
the practice in early releases of the NetView program.
v COLLECT can cause a complex pipeline to become deadlocked or clogged. For
information on resolving clogged pipelines, see “Clogged Pipelines” on page
346.
Example: Converting Single-Line Messages to Multiline
To present the output of LIST STATUS=TASKS as a multiline message, enter:
PIPE NETVIEW LIST STATUS=TASKS
| COLLECT
| CONSOLE
The many single-line messages issued by LIST are saved by COLLECT until all
output of the NETVIEW stage has been gathered. Then a single MLWTO is
produced. If this stage is running in a remote autotask (using RMTCMD), then the
processing effort for the network is far less for the one multiline message than for
the many single-line messages.
Example: Displaying Multiline Messages and Preserving Output
Structure
In the following example the 'IST350I DISPLAY TYPE = LINES' is removed without
disturbing the multiline structure of the output; IST097 is by itself and the others
are together.
PIPE CORRCMD D NET,LINES
| SEPARATE
| NLOCATE 1.7 /IST350I/
| COLLECT ASBEFORE
| CONSOLE
---> IST097I DISPLAY ACCEPTED
--->
IST354I PU T4/5 MAJOR NODE = NT7EVTAM
IST172I NO LINES EXIST
IST231I CA MAJOR NODE = NT7ECTCA
IST170I LINES:
IST080I CTCALN7E ACTIV----E
IST314I END
See also the example in the LOGPROF1 stage list (CNME1049).
Example: Formatting LIST STATUS=TASKS Output
In the following example the common information contained in all LIST
STATUS=TASKS messages, normally found in each output line, is presented in
multiple label lines before presenting the data.