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

PIPE SEPARATE
SEQUENCE
Specifies that the lines are output to the output streams in sequence. The first
line is output to the primary output stream. The second line is output to the
secondary output stream, and so on, for as many output streams as are
defined. All remaining lines are passed as single-line messages to the last
defined output stream.
If only the primary output stream is defined, all lines are output to that
stream. If only a secondary stream is defined, for example, when specifying
NOT SEPARATE, all lines, except the first line, are output to the secondary
stream.
Usage Notes
Examples
212 Programming: Pipes
v SEPARATE cannot be the first stage.
v SEPARATE directly affects the way that messages in the pipeline are displayed,
logged, and searched by other stages.
v SEPARATE can be useful preceding stages that search for matches to a delimited
string within a record.
v SEPARATE has no effect on single-line messages.
Example: Breaking a Multiline Message into Single-Line
Messages
To issue the D NET,CDRMS command, allow time for asynchronous messages to
return from VTAM, and break the multiline messages into single-line messages,
enter:
PIPE NETVIEW D NET,CDRMS
| CORRWAIT 10
| SEPARATE
| CONSOLE
Example: Breaking a Multiline Message, Selecting from and
Displaying the Results
This example issues a TASKUTIL command, separates multiline messages into
single lines, selects messages with occurrences of OPER1 or OPER2, collects them
into a multiline message, and displays them.
PIPE NETVIEW TASKUTIL
| SEPARATE
| LOCATE /OPER1/ /OPER2/
| COLLECT
| CONSOLE
Example: Separating Data Lines from Control and Label Lines
This example shows how to separate data lines from control and label lines into
two pipeline streams.
PIPE (END %)
| ... /* stages creating input stream */
| A: SEPARATE DATA
| ... /* stages processing data lines */
%A:
| ... /* stages processing control/label lines */