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.

stages have a third stream, which is called the tertiary stream. Streams 4 through<br />

10 are referred to only by their stream numbers.<br />

There are two additional data stream terms to understand:<br />

Defined<br />

A data stream is defined when the pipeline specification calls <strong>for</strong> data to<br />

flow between two stages. For example, the following pipeline displays HI<br />

THERE on the console:<br />

PIPE LITERAL /HI THERE/<br />

|CONSOLE<br />

In this case, the CONSOLE stage has one input and no output stream<br />

defined. The input is from the LITERAL /HI THERE/ stage. In stages that do<br />

not allow multiple input and output streams, the position of the stage<br />

within the pipeline specification defines how the data will flow to and<br />

from the stage.<br />

The primary input and output streams are usually defined by the position<br />

of the stage specification within the pipe specification. The primary input,<br />

if required, is usually from the previous stage within the pipe specification.<br />

The primary output is usually to the following stage within the pipe<br />

specification, unless the stage is the last stage within the pipeline<br />

specification. In the latter case, the primary output differs depending on<br />

the individual stage.<br />

Streams, other than the primary input and primary output, are defined<br />

using labels. For in<strong>for</strong>mation on labels and complex pipelines, see<br />

“Complex Pipelines” on page 7.<br />

Connected<br />

Data streams are connected and disconnected during the processing of the<br />

pipeline. A data stream is connected until the stages connected to the data<br />

stream disconnect. A stage will disconnect when a condition, specific to the<br />

stage, is encountered. Most stages retain their connections until they<br />

terminate. When a stage disconnects its output stream, the corresponding<br />

input stream will disconnect as soon as any messages being passed<br />

through the stream have been read in, or consumed, by the partner stage.<br />

For example, in Figure 7, Stage A and Stage B are connected by a data<br />

stream. The output stream of Stage A is the input stream of Stage B. Stage<br />

A completes processing and disconnects. Only after Stage B completes<br />

reading any messages sent from Stage A does the data stream itself<br />

disconnect.<br />

Output Input<br />

Data<br />

Stage A Stage B<br />

Stream<br />

Figure 7. Input and Output Data Streams<br />

Introduction and Concepts<br />

Note: Defined is the state of the stream as coded in the pipeline specification and<br />

connected is the status of the stream during pipeline processing.<br />

Chapter 1. <strong>NetView</strong> Pipelines Introduction and General Concepts 5

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

Saved successfully!

Ooh no, something went wrong!