28.11.2012 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

PIPE COLLECT<br />

Streams<br />

40 <strong>Programming</strong>: <strong>Pipes</strong><br />

If a secondary input stream is not defined <strong>for</strong> the COLLECT stage and FREEFORM<br />

is not specified:<br />

v If the first line of a multiline message is a data line, it is handled as a control<br />

line.<br />

v For each multiline message produced, COLLECT l accepts up to six label lines<br />

from the primary input stream. These lines must have previously been<br />

designated as label lines.<br />

v All lines after the sixth, or after the first data line, are handled as data lines<br />

regardless of how they were previously designated.<br />

v The last line received on the primary input stream is used as an end line.<br />

Stream Type Number Supported<br />

Input 2<br />

Output 1<br />

Termination Conditions<br />

COLLECT terminates when the primary input stream or the output stream is<br />

disconnected.<br />

Operand Descriptions<br />

If no operands are given, COLLECT creates one multiline message containing all<br />

input lines, and must delay its output until the previous stage disconnects.<br />

AFTER<br />

Specifies that the message containing the matching string is appended to<br />

whatever is collected at that point.<br />

ASBEFORE<br />

Specifies that the output is collected as it was previously. This usually applies<br />

to messages obtained using the SEPARATE stage, but can also apply to<br />

messages replicated exactly using other techniques.<br />

AT Discard the entire message containing the matching string. This is the default<br />

value.<br />

BEFORE<br />

Specifies that when the message containing the matching string is detected, it<br />

is kept to begin a new multiline message and is not part of the output<br />

produced.<br />

BREAK<br />

Causes collected lines to be issued when a string match is detected. A<br />

delimited string is required if BREAK is used. See the AT, AFTER, and<br />

BEFORE keywords <strong>for</strong> disposition of the message containing the matching<br />

string.<br />

FREEFORM<br />

No validation of the existing line types of input message is per<strong>for</strong>med. As a<br />

result, the line types are not modified by the COLLECT stage. For example, if a<br />

message with a line type of Control follows a message with a line type of<br />

Data, and a message with a line type of Data follows a message with a line<br />

type of End, the collected multiline message is built with this erroneous<br />

sequence.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!