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
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
PIPE LOOKUP<br />
160 <strong>Programming</strong>: <strong>Pipes</strong><br />
Operand Descriptions<br />
APPEND<br />
Specifies that LOOKUP append the matching reference record to the detail<br />
record be<strong>for</strong>e writing the detail record to the primary output stream. If the<br />
detail record is a single line, the resulting output is a multiline message<br />
consisting of the detail record and the reference record. If the detail record is a<br />
multiline message, the multiline message is extended when the reference<br />
record is added to it.<br />
detail_position.length<br />
Specifies the starting position and length within the detail record to be<br />
compared to the reference records. The default is 1.*, which indicates that each<br />
detail record beginning at the first character <strong>for</strong> the entire length of the record<br />
is compared to the reference records.<br />
Detail_position can be any positive number.<br />
Length can be any positive number or an *. An asterisk (*) indicates that all<br />
characters in the message beginning at the position indicated by detail_position<br />
are compared. If length is not specified, length defaults to 1.<br />
reference_position.length<br />
Specifies the starting position and length of the reference records to be used in<br />
the comparison with each detail record. If detail_position.length is specified, the<br />
default <strong>for</strong> reference_position.length is the same value as the detail_position.length<br />
value.<br />
Reference_position can be any positive number.<br />
Length can be any positive number or an *. An asterisk (*) indicates that all<br />
characters in the message beginning at the position indicated by<br />
reference_position are compared. If length is not specified, the length default is 1.<br />
WILDCARD<br />
The optional keyword WILDCARD must be followed by a delimited string of<br />
exactly three characters.<br />
The first character, x, is the character contained in the reference record<br />
indicating that any single character found in the detail records at that point is<br />
considered a match. A typical value <strong>for</strong> x is a question mark (?).<br />
For example, if WILDCARD /? / is specified, and the reference record is ABCD?,<br />
then only detail record fields that are exactly 5 characters long with the first<br />
four characters being ABCD are considered a match.<br />
The second character, y, is the character contained in the reference record<br />
indicating that any number of characters found in the detail records at that<br />
point are considered a match. A typical value <strong>for</strong> y is an asterisk (*).<br />
For example, if WILDCARD /?* / is specified, and the reference record is ABCD*,<br />
then detail record fields at least 4 characters long beginning with ABCD are<br />
considered a match.<br />
The third character, z, indicates the exception to the x value. Any single<br />
character in the character position indicated by x is considered a match unless<br />
that position contains the character indicated by z. Typically z is disabled by<br />
being specified as a blank.<br />
For example, if WILDCARD /?**/ is specified and the reference record is A?CD*,<br />
then the following items are considered a match:<br />
v Detail record fields at least 4 characters long beginning with an A, and
Change language