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

RIGHT (conversion order)<br />

Specifies that the input data is to be truncated or padded to the length<br />

specified by number. Characters are counted from the end, or right, of the<br />

input. If padding is required, the character specified on the most recent PAD<br />

global order is used.<br />

RVAR (conversion order)<br />

From input revision variable name, returns the current value.<br />

STRIP (conversion order)<br />

Specifies that padding characters at the start or end of the data are to be<br />

removed. The padding character is defined by the most current PAD global<br />

order specification within the edit phrase.<br />

STRIPL (conversion order)<br />

Specifies that padding characters at the beginning of the data are to be<br />

removed. The padding character is defined by the most current PAD global<br />

order specification within the edit phrase.<br />

STRIPR (conversion order)<br />

Specifies that any padding characters at the end of the data are to be removed.<br />

The padding character is defined by the most current PAD global order<br />

specification within the edit phrase.<br />

SUBSTR (conversion order)<br />

Specifies that a subset of the input data is to be selected. Position.length<br />

indicates the starting position and length of data to be selected. For<br />

in<strong>for</strong>mation about defining position.length, see “position.length” on page 92.<br />

If padding is required <strong>for</strong> the data to be the required length, the characters<br />

specified by the most current PAD global order is used.<br />

UPCASE (conversion order)<br />

UPCASE translates the standard 26-character Latin letters (as defined in code<br />

page 037) to uppercase.<br />

V2C (conversion order)<br />

Specifies that the input data is a displayable string and is to be converted to a<br />

variable length string prefixed with a 2-byte, unsigned length value.<br />

V2C is the inverse of C2V.<br />

This conversion order is particularly useful when dealing with data interacting<br />

with the SQL pipe stage.<br />

X2C (conversion order)<br />

Specifies that the input data is converted from displayable hexadecimal<br />

notation to internal binary representation. For example, if the input is X'C1C2',<br />

C2X returns the hexadecimal values X'AB'. The resulting hexadecimal value is<br />

half the length of the original.<br />

X2C is the inverse of C2X.<br />

YESNO (conversion order)<br />

Specifies that the first byte of the input data is converted from a bit string to a<br />

value of Yes or No. If any bit in the first byte is a one (1), Yes is returned. If all<br />

bits in the first byte are zero (0), No is returned. The case of the character string<br />

is exactly as displayed, Yes or No.<br />

This conversion order is particularly useful when using the IFRAUCPY,<br />

IFRAUPPT, IFRAUPRI, and IFRAUSEC msgattr input orders.<br />

Chapter 2. Pipeline Stages and Syntax 115

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

Saved successfully!

Ooh no, something went wrong!