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.

Where:<br />

stage_name<br />

Is any <strong>NetView</strong> PIPE stage.<br />

See “PIPE Stages” on page 24 <strong>for</strong> an alphabetic listing and brief summary of each<br />

PIPE stage.<br />

Operand Descriptions<br />

DEBUG<br />

Generates connection and data stream trace in<strong>for</strong>mation that can be used to<br />

debug pipelines. DEBUG, when used as a PipeOption, must have one of the<br />

following items specified:<br />

1 Produce debug output <strong>for</strong> all pipeline stages. This is the same as coding<br />

(DEBUG) on each stage.<br />

2 Produce additional debug in<strong>for</strong>mation whenever a BNH155E message is<br />

generated. BNH155E indicates that the pipeline is clogged. The additional<br />

in<strong>for</strong>mation produced by DEBUG 2 can help you diagnose the clog.<br />

END<br />

ESC<br />

Both DEBUG 1 and DEBUG 2 can be specified in the same pipeline<br />

specification.<br />

For more in<strong>for</strong>mation on the DEBUG option see Chapter 8, “Debugging<br />

<strong>NetView</strong> Pipelines,” on page 345.<br />

The end character allows multiple, simple pipelines to operate within a<br />

complex pipeline. The pipeline specification, included after the end character,<br />

operates independently of the pipeline specified be<strong>for</strong>e the end character. The<br />

end character, with stage labels, and stages with multiple input or output<br />

streams is used to create complex pipelines. For in<strong>for</strong>mation on creating<br />

complex pipelines, see “Complex Pipelines” on page 7.<br />

The valid value of END can be a character acceptable <strong>for</strong> STAGESEP, but the<br />

value cannot be the same value as STAGESEP or ESC in the same PIPE<br />

command.<br />

If you want to include the end character within your pipe where it must not be<br />

interpreted as an end character, you can either include the ESC character<br />

immediately be<strong>for</strong>e it or use the “self escape” technique. Two side-by-side<br />

END characters resolve to one character taken literally. For example, if your<br />

ESC character is defined as % and your END character is defined as ?, use<br />

either of the following examples:<br />

PIPE (END ?) LITERAL ’MY END CHARACTER IS ??’<br />

| CONSOLE<br />

PIPE (ESC % END ?) LITERAL ’MY END CHARACTER IS %?’<br />

| CONSOLE<br />

The following text is displayed on the console:<br />

MY END CHARACTER IS ?<br />

Pipeline Stages and Syntax<br />

Indicates that the character following the specified character is treated literally<br />

when the pipeline specification is parsed. For example, if you specify STAGESEP<br />

| ESC % as options and the string ABC%|XYZ is encountered in the pipeline<br />

Chapter 2. Pipeline Stages and Syntax 21

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

Saved successfully!

Ooh no, something went wrong!