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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PIPE COUNT<br />

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

Operand Descriptions<br />

Usage Notes<br />

BYTES<br />

Specifies that the total bytes in all messages received on the input stream are to<br />

be passed to the primary output stream. Both leading and trailing blanks are<br />

counted.<br />

EACHLINE<br />

Specifies that COUNT set a line attribute in each message line indicating the<br />

line's position within the data stream. The modified line is passed to the<br />

primary output stream. A secondary output stream is not supported.<br />

The line attribute can be accessed with EDIT LINECOUNT and CONSOLE<br />

DUMP.<br />

The line attribute remains unchanged in the pipeline and in safes created by<br />

the SAFE stage. However, commands executed subsequently in the pipeline<br />

can change the line count attributes.<br />

See “Example: Line Counts Reset by Command” on page 61 <strong>for</strong> in<strong>for</strong>mation on<br />

modification of set line attributes, see HELP PIPE EDIT <strong>for</strong> in<strong>for</strong>mation on the<br />

EDIT stage, and HELP PIPE CONSOLE <strong>for</strong> in<strong>for</strong>mation on the CONSOLE<br />

stage.<br />

Note: Do not use EACHLINE if the processed messages are to be used with<br />

the REPLY command.<br />

EACHMSG<br />

Specifies that COUNT set a message attribute in each message indicating the<br />

message's position within the data stream. The modified message is passed to<br />

the primary output stream. A secondary output stream is not supported.<br />

The message attribute remains unchanged in the pipeline and in safes created<br />

by the SAFE stage. However, message count attributes are reset if the message<br />

is processed by a NETVIEW or CORRCMD stage.<br />

FROM<br />

Specifies the initial value <strong>for</strong> the counter. The default is zero.<br />

LINES<br />

Specifies that the total number of lines in all messages received on the input<br />

stream is to be passed to the primary output stream.<br />

MAXLINE<br />

Specifies that COUNT counts each message line passed to it and returns the<br />

number of bytes contained in the longest line. Both leading and trailing blanks<br />

are counted.<br />

MESSAGES<br />

Specifies that the total number of messages passed on the input stream is<br />

passed to the primary output stream.<br />

Each multiline message is counted as one message.<br />

MINLINE<br />

Specifies that COUNT counts each message line passed to it and returns the<br />

number of bytes contained in the shortest line. Both leading and trailing blanks<br />

are counted.<br />

v If you do not want leading and trailing blanks to be counted when using<br />

COUNT BYTES, add a STRIP stage be<strong>for</strong>e the COUNT BYTES stage.

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

Saved successfully!

Ooh no, something went wrong!