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.

Termination Conditions<br />

If specified as a first stage, STEM and $STEM terminate when the output stream<br />

disconnects or when the end of the data stored is reached. If specified as a<br />

subsequent stage, STEM and $STEM terminate when the input stream disconnects.<br />

Operand Descriptions<br />

PIPE STEM and PIPE $STEM<br />

(COMMON)<br />

Specifies that the common global variable dictionary is accessed instead of<br />

your personal variable dictionary.<br />

(TASK)<br />

Specifies that the task global variable dictionary is accessed instead of your<br />

personal variable dictionary.<br />

APPEND<br />

Specifies that new data is appended as additional STEM variables following<br />

STEM data that already exists as determined by the count in element zero.<br />

APPEND can be used only on a stage that is not first.<br />

The APPEND option is not enabled if STEM is the first stage. For processing of<br />

the APPEND option, the record count of the STEM variable must be zero or<br />

positive.<br />

COLLECT<br />

Causes STEM to build one multiline message instead of many single-line<br />

messages. COLLECT is allowed only when STEM is the first stage in a<br />

pipeline. Using the COLLECT operand on the STEM stage is the functional<br />

equivalent of using the STEM stage followed by the COLLECT stage, but it is<br />

faster and uses less storage. Collect can only be used on a first stage.<br />

stemroot<br />

Specifies the name of the STEM variable to read from or write to. End it with a<br />

period (.) if you are using a REXX command procedure. Do not include an<br />

ampersand (&) in the name (an ampersand is implied in the <strong>NetView</strong><br />

command list language). The name length (name plus appended STEM count)<br />

can be up to 11 characters in the <strong>NetView</strong> command list language and up to 31<br />

characters in REXX and HLL except when $STEM is used, in which case, the<br />

limits are 10 and 30, respectively. Lowercase characters in the name are<br />

changed to uppercase be<strong>for</strong>e being processed. The &1 - &31 variables as used<br />

in the <strong>NetView</strong> command list language are not supported <strong>for</strong> use in the STEM<br />

stage. However, you can assign these values to or from other named variables,<br />

which you can use in the STEM stage.<br />

The record count <strong>for</strong> the STEM variable is name with a zero appended to it.<br />

The count indicates how many records the STEM variable contains. The STEM<br />

records are composed of name with a numeric value appended.<br />

(number)<br />

Specifies the number invocations (generations) to refer when setting the<br />

variables. The number of generations refers to the current nesting level within<br />

the REXX, PL/I, or C calling sequence.<br />

(Number) must be zero (0) or greater, and less-than or equal-to the existing<br />

number of generations. If (number) is greater than (0), the variables are in a<br />

generation preceding the current generation. The specified generation can<br />

precede the generation from which the PIPE command is issued if such a<br />

generation exists.<br />

Chapter 2. Pipeline Stages and Syntax 227

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

Saved successfully!

Ooh no, something went wrong!