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

PIPE VARLOAD<br />

Syntax<br />

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

VARLOAD:<br />

VARLOAD<br />

(0)<br />

(COMMON)<br />

(TASK)<br />

(number)<br />

Command Description<br />

The VARLOAD stage is used to set values <strong>for</strong> variables that are passed in the<br />

input stream. The names and values of the variables set by VARLOAD are<br />

specified by the records passed on the primary input stream. VARLOAD sets one<br />

variable <strong>for</strong> each input message containing a character other than a blank or<br />

asterisk in the first position of the record. Messages beginning with a blank or<br />

asterisk are ignored. All other messages are treated as delimited strings.<br />

The use of the VARLOAD stage is limited to the command procedure<br />

environments (REXX, <strong>NetView</strong> command list language, and HLL). However, if the<br />

(COMMON) or (TASK) option is used, VARLOAD can be invoked from message<br />

automation, by command originating at the PPT task or an optional task, or by<br />

using a labeled command originating in a command procedure. Use of the<br />

VARLOAD stage outside of these environments results in message DSI290I and<br />

termination of the pipeline.<br />

Data passed to VARLOAD on the input stream can be in one of two <strong>for</strong>mats:<br />

v /variable1/value<br />

v /variable1=variable2/value<br />

If /variable1/value is specified, the variable name following the delimiter is set to the<br />

value after the second delimiter. In the /variable1=variable2/value case, the current<br />

value of variable1 is compared to the value of variable2. If they are equal, variable1 is<br />

set to the value following the second delimiter. This is equivalent to the compare<br />

and swap <strong>OS</strong>/390 function.<br />

Notes:<br />

1. Variable1 is read from the dictionary specified by (COMMON), (TASK), or<br />

(number).<br />

2. Variable2 is read from the local dictionary.<br />

3. If variable1=variable2 is specified and is contained in a multiline message, all<br />

multiline message comparisons are done first. If any comparison fails, no<br />

variables are updated from the message data.<br />

You can control which comparisons are grouped together using COLLECT and<br />

SEPARATE.<br />

All messages from the input stream are also written to an output stream. If a<br />

secondary output stream is defined, the following items are written to the<br />

secondary output stream:<br />

v All input messages with errors in the variable name

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

Saved successfully!

Ooh no, something went wrong!