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.

PIPE VAR and PIPE $VAR<br />

252 <strong>Programming</strong>: <strong>Pipes</strong><br />

Termination Conditions<br />

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

disconnected or when it finishes processing. If specified as a subsequent stage,<br />

VAR and $VAR terminate when the input stream is disconnected or when all<br />

variables are set and the output stream is disconnected.<br />

Operand Descriptions<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 />

name<br />

Specifies the name of the variable to read-from or write-to. Do not include an<br />

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

command list language). The name length can be up to 11 characters in the<br />

command list environment and up to 31 characters in REXX and HLL except<br />

when $VAR is used. When $VAR is used, the limits are 10 and 30, respectively.<br />

Lowercase characters in the name are changed to uppercase be<strong>for</strong>e being<br />

processed. The &1 - &31 variables as used in the <strong>NetView</strong> command list<br />

language are not supported <strong>for</strong> use in the VAR stage. However, you can assign<br />

these values to, or from, other named variables, that you can use in the VAR<br />

stage.<br />

The amount of variable names is unlimited.<br />

(number)<br />

Specifies the number invocations (generations) to refer back 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 />

The default <strong>for</strong> (number) is zero (0).<br />

Usage Notes<br />

The following conditions apply to both VAR and $VAR stages:<br />

v If (COMMON) or (TASK) is specified, VAR does not require the PIPE to be<br />

issued from a procedure.<br />

v When VAR is the first stage of a pipeline specification, the following conditions<br />

apply:<br />

– The maximum size of a message buffer output from the VAR stage is 32000<br />

bytes. Message buffers exceeding 32000 bytes are truncated to 32000 bytes.<br />

– In the REXX environment, if the variable specified on the VAR stage has not<br />

been initialized, the output value is the variable name.<br />

– For the <strong>NetView</strong> command list language and HLL environments, if the<br />

variable specified on the VAR stage has not been initialized, the output value<br />

is a null message (an automation internal function request with a single,<br />

zero-length message buffer).

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

Saved successfully!

Ooh no, something went wrong!