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

PIPE CHANGE
Streams
34 Programming: Pipes
The contents of msgSource is the source of messages to be changed. The contents of
the changeSpecs. stem is the key to the advanced functions. The CHANGE stage
expects the lines in the changeSpecs. stem to be in groups of three, where each
group of lines has the following syntax:
First line::
position.length
Second line::
string1
Third line::
string2
R
I
See “Example: Using CHANGE with parameters from secondary input” on page 36
for an example of using a secondary input stream.
Notes:
1. The forward slash characters (/) in the syntax diagrams are for illustration. Any
character except alphanumeric characters, parentheses, blanks, nulls, and
national characters (@, #, and $) can be used instead of the slash character to
delimit the strings.
2. Changes are applied in the order in which they are supplied, so some strings
inserted by early changes might be modified by later changes. There is still a
maximum that you can specify for the number of changes to any one message;
that maximum is still specified as an argument on the CHANGE stage.
Stream Type Number Supported
Input 2
Output 2
Termination Conditions
The CHANGE stage ends when the primary input stream disconnects or when
both output streams disconnect.
Operand Descriptions
numchg
The maximum number of substitutions to be made in each message. Note that
there can be multiple lines per message. If numchg is not specified, the default
is to change all occurrences in each message.
position.length
Specifies the character position in each message where searching begins, and
the length of the search. If you specify a length of *, the remainder of each line