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.

Online Help Facility<br />

v The stage detects that its termination conditions have been reached. See the<br />

stage descriptions in Chapter 2, “Pipeline Stages and Syntax,” on page 19 <strong>for</strong><br />

more in<strong>for</strong>mation.<br />

v The stage detects that there is no more data to read from a device (<strong>for</strong> device<br />

drivers only).<br />

v The pipeline becomes clogged. A deadlock occurs between the data streams<br />

within a complex pipeline.<br />

You can obtain in<strong>for</strong>mation about the PIPE command and stages with the <strong>NetView</strong><br />

online help facility. To display online help <strong>for</strong> the pipe command, enter:<br />

HELP PIPE SYNTAX<br />

To display online help <strong>for</strong> a specific stage name, enter:<br />

HELP PIPE stage_name<br />

Where: stage_name is any <strong>NetView</strong> PIPE stage.<br />

Getting Started with <strong>NetView</strong> Pipelines<br />

The PIPE command specification consists primarily of options and stage<br />

specifications with a stage separator between each stage. The default stage<br />

separator character is usually a vertical bar (|) on 3270 terminals, but might be a<br />

split vertical bar (¦) on workstation terminals.<br />

The following examples use several pipeline specifications to manipulate messages<br />

in different ways. They are intended to show basic pipeline possibilities without<br />

exploring all the filters and device drivers available. For more in<strong>for</strong>mation on other<br />

filters, see Chapter 4, “<strong>NetView</strong> Pipeline Filters,” on page 303. For in<strong>for</strong>mation on<br />

device drivers, see Chapter 3, “<strong>NetView</strong> Pipelines Device Drivers,” on page 283.<br />

As an example, consider two fictitious people and a fictitious event: Pete and Sam<br />

planning their annual vacation. They have created a member named WISHLIST in<br />

a partitioned data set that is associated with the DSIPARM ddname. WISHLIST<br />

contains travel in<strong>for</strong>mation, including sites to see and various attractions. Pete and<br />

Sam are working in an MVS environment.<br />

Pete decides to write a PIPE command that will list all the destinations on their<br />

list.<br />

He enters on the command line:<br />

PIPE < WISHLIST | CONSOLE<br />

The < (From Disk) stage accesses a disk file and writes its contents to the pipeline,<br />

thus bringing data into the pipeline. The complete stage specification <strong>for</strong> the <<br />

(From Disk) stage is < WISHLIST, which consists of the stage name,

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

Saved successfully!

Ooh no, something went wrong!