IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

PIPE CHANGE
Syntax
Synonyms
CHANGE (with specifications as arguments):
CHANGE
1.*
position.length
/string1/string2/
/string1/ /string2/ numchg
CHANGE (with parameters from secondary input):
CHANGE
numchg
Stage Name Synonym
CHANGE CHAN
Command Description
The CHANGE stage replaces occurrences of the first specified string with the
second string. Either string can be null. If the first string is null, the second string
is inserted at the beginning of each line. If the second string is null, all occurrences
of the first one are deleted. Data between substitutions are copied without change.
If a secondary output stream is defined, then messages in which a change was
made are passed to the primary output stream and messages in which no changes
were made (because the first string is not found) are passed to the secondary
output stream. If either output stream is defined, but disconnected, messages
usually sent to the disconnected output stream are discarded. If no secondary
output stream is defined, then all changed and unchanged messages are passed to
the primary output stream.
You can also specify a secondary input stream to the CHANGE stage (see the
syntax diagram above labeled CHANGE (with parameters from secondary input)).
Because this method provides an alternate means of providing parameters for
input (rather than through the use of arguments), using secondary input is
particularly useful when there is a need to make many changes, or a number of
changes that are computed (rather than predetermined). This also provides a
means of specifying strings longer than 255.
Consider a pipe that might be coded like this:
PIPE (END %)
| A: CHANGE
| CONSOLE
% STEM changeSpecs.
|A:
PIPE CHANGE
Chapter 2. Pipeline Stages and Syntax 33