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 INTERPRT<br />

Syntax<br />

Synonyms<br />

INTERPRT:<br />

INTERPRT<br />

*<br />

Stage Name Synonym<br />

INTERPRT INT<br />

Command Description<br />

INTERPRT builds stages from stage specifications that you supply to the PIPE<br />

command as its current message. You can use INTERPRT when creating your stage<br />

specifications dynamically, or when your PIPE command is too long <strong>for</strong> the<br />

processing environment. For example, the <strong>NetView</strong> Command List Language<br />

restricts commands to 240 characters. If your pipeline specification is longer than<br />

this, you can create a multiline message, each line of which is a complete stage<br />

specification. You provide this message to your PIPE command generally by using<br />

another, outer pipeline.<br />

Streams<br />

The stage specifications coded must be considered to be complete stage<br />

specifications. The INTERPRT stage does not expect any stage separator or escape<br />

characters to be supplied, and any encountered is taken literally. However, it can<br />

be appropriate <strong>for</strong> the complete stage specification to contain a stage separator, or<br />

escape character within it, such as is appropriate if a complete PIPE command is<br />

coded on the NETVIEW stage.<br />

Often, the stages are read into the pipeline by way of the STEM stage. They are<br />

processed by the INTERPRT stage as an inner pipeline in a PIPE-within-a-PIPE<br />

structure.<br />

Stream Type Number Supported<br />

Input 1<br />

Output 1<br />

Termination Conditions<br />

INTERPRT modifies the stages in the current message. Because it is a pipeline<br />

builder stage, INTERPRT does not have its own termination conditions. See the<br />

in<strong>for</strong>mation on the stages INTERPRT is modifying <strong>for</strong> termination conditions.<br />

Operand Descriptions<br />

PIPE INTERPRT<br />

* Specifies that the current message is to be processed by INTERPRT. Asterisk (*)<br />

is the default.<br />

Chapter 2. Pipeline Stages and Syntax 143

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

Saved successfully!

Ooh no, something went wrong!