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.

Position can be any positive or negative number. A negative value <strong>for</strong> position<br />

indicates that the starting position is to be counted from the end of the line,<br />

rather than from the beginning.<br />

Length is an unsigned positive number indicating the number of characters<br />

from position to be processed. An asterisk (*) can be specified <strong>for</strong> length<br />

indicating that all characters after position are to be used. Position without<br />

length and the period (.) separator defaults length to 1.<br />

If length is larger than the available characters, all available characters are used.<br />

The LEFT conversion order can be used to pad the resulting text if required.<br />

Consider the following message:<br />

PIPES CAN BE FUN!<br />

This... Results in...<br />

1.* PIPES CAN BE FUN!<br />

+7.6 CAN BE<br />

-7.* BE FUN!<br />

9.20 N BE FUN!<br />

8 A<br />

-25.5 a null string is returned<br />

-18.3 PI<br />

number<br />

An unsigned positive number. See the descriptions <strong>for</strong> the orders using number<br />

to determine the meaning of number.<br />

/string/<br />

A delimited character string. When used as an input order, /string/ defines a<br />

literal to be used as input. See the descriptions <strong>for</strong> other orders using /string/ to<br />

determine the meaning of /string/.<br />

The plus sign (+), minus sign (−), and asterisk (*) have special meanings in edit<br />

scripts. To avoid confusion, do not use these characters as /string/ delimiters in<br />

edit scripts.<br />

Global Orders<br />

Global orders specify common processing actions <strong>for</strong> all parts of the subsequent<br />

edit phrase.<br />

CBETEMP (global order)<br />

CBETEMP is used to read in a Common Base Event template. The CBETEMP<br />

order reads in the template as a secondary chain of <strong>NetView</strong> buffers. The<br />

READCBE and READSRC global orders can be used to switch the primary<br />

input source <strong>for</strong> the EDIT phrase. This order is primarily intended <strong>for</strong> use by<br />

the EDIT automation table action in order to build a Common Base Event from<br />

a message or from an MSU.<br />

The following parameter is required:<br />

template_name<br />

The name of the Common Base Event template, corresponding to the<br />

name= attribute on a tag in the template file.<br />

A simple phrase to create a CBE from a message is:<br />

CBETEMP /msgdefault/ COPY *<br />

PIPE EDIT<br />

Chapter 2. Pipeline Stages and Syntax 93

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

Saved successfully!

Ooh no, something went wrong!