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

argument. Note that FINDLINE 1 is equivalent to TOPLINE. If the number<br />

specified is greater than the number of lines in the current message, a null line<br />

is used <strong>for</strong> subsequent input orders.<br />

If the number is negative, EDIT counts from the end of the message. For<br />

example, LINE -1 selects the last line of a multiline message and LINE -2<br />

selects the next to last line. LINE 0 (zero) results in a null line.<br />

FINDLINE /string/ (global order)<br />

Advances the current line <strong>for</strong>ward to a line containing the specified target<br />

string, which then becomes the current line. If no line after the current line<br />

contains the target, a null line is used <strong>for</strong> subsequent input orders.<br />

FWDLINE n (global order)<br />

Moves the current line ahead by the number specified.<br />

LASTLINE (global order)<br />

Cancels all previous READLINE orders and per<strong>for</strong>ms a RESET. Input is set to<br />

the last line of the multiline message.<br />

LASTLINE is a complementary function to TOPLINE. Where LASTLINE sets<br />

the input to the last line, TOPLINE sets the input to the first line of the<br />

multiline message.<br />

See also TOPLINE.<br />

LOGTO (global order)<br />

Sets an option such that if the message is presented <strong>for</strong> display using either the<br />

CONSOLE stage or the ROUTE stage, the message is logged. One of these<br />

arguments is required:<br />

N This action is <strong>for</strong> the net log.<br />

S This action is <strong>for</strong> the system log.<br />

H This action is <strong>for</strong> the hardcopy log.<br />

* This action is <strong>for</strong> all three log methods: net log, system log, and<br />

hardcopy log.<br />

Usage Notes:<br />

1. If the message is automated, then automation can override the logging<br />

options set by EDIT. If the message is delivered to a distributed autotask,<br />

then the log options are honored on the local domain, but is reset to default<br />

values by RMTCMD message <strong>for</strong>warding. Also, if a message is routed<br />

directly to a remote domain, the options are reset to default values.<br />

2. Messages that are exposed <strong>for</strong> logging are always written to the CanzLog<br />

file. You can control visibility of your messages in the CanzLog file by<br />

using the TAG keyword of the LOGTO stage.<br />

NAMEBIND (global order)<br />

NAMEBIND writes the value of the /name/ and the text previously produced<br />

by other output orders, if any, to a new output line. Both the /name/ and the<br />

output line data are preceded in the output line by a halfword length value.<br />

The message ID (HDRMTYPE) and the line counter meet the name binding<br />

requirements <strong>for</strong> events sent to the <strong>NetView</strong> Alert and Message Adapters.<br />

Lines created by NAMEBIND can be transferred to the adapter using the PPI<br />

stage. Examples of NAMEBIND can be found in “Example: Sending an Alert to<br />

the <strong>NetView</strong> Alert Adapter” on page 120, CNMEALUS, and CNMEMSUS. For<br />

more in<strong>for</strong>mation about PPI, see “PIPE PPI ” on page 187.<br />

To create a valid adapter name/value pair binding, do one of these items:<br />

v Copy the original contents of the automated alert or message to the output<br />

using a COPY * EDIT order.<br />

Chapter 2. Pipeline Stages and Syntax 95

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

Saved successfully!

Ooh no, something went wrong!