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.

Usage Notes<br />

PIPE PPI<br />

When PPI is used as a sender, receiver_name can also be an asterisk (*). Asterisk<br />

indicates that the message is to be returned to the program originating the<br />

message. The originating message is identified by the sender message attribute<br />

(IFRAUSDR).<br />

APONLY<br />

Specifies that messages are accepted only from an APF authorized program.<br />

DATAONLY<br />

Specifies that only the data portion of each line is sent. <strong>NetView</strong> buffer headers<br />

and structures are not sent. DATAONLY is only valid when PPI is used as a<br />

sender.<br />

MLWTO<br />

Specifies that the message receiver can receive messages <strong>for</strong>matted to <strong>NetView</strong><br />

multiline message standards. Messages are sent as a <strong>NetView</strong> multiline<br />

message unit. MLWTO is only valid when PPI is used as a sender.<br />

NV Specifies that the receiver is another <strong>NetView</strong>. Multiline messages and<br />

attributes are sent to the receiver who reconstructs them into a multiline<br />

message.<br />

TECROUTE<br />

Specifies that the message or alert is to be <strong>for</strong>matted and transferred to the<br />

Event/Automation Service associated with the named PPI receiver. The<br />

message is converted by the Event/Automation Service into an Event<br />

Integration Facility (EIF) event and sent to the server.<br />

TECRTCFM<br />

Specifies that the message or alert is to be <strong>for</strong>matted and transferred to the<br />

Event/Automation Service associated with the named PPI receiver. The<br />

message or alert is converted by the Event/Automation Service into an an<br />

Event Integration Facility (EIF) event and sent to a server. The<br />

Event/Automation Service expects the server to send a reply confirming or<br />

rejecting the EIF event.<br />

TRAPROUT<br />

Specifies that the alert is to be <strong>for</strong>matted and transferred to the<br />

Event/Automation Service associated with the named PPI receiver. The alert is<br />

converted by the Event/Automation Service into a trap and sent to the SNMP<br />

manager. Note that text messages are not supported by TRAPROUT.<br />

/string/<br />

A delimited character string to be sent to the receiver specified by<br />

receiver_name.<br />

v It is imperative, when passing an alert to the alert adapters, to send the entire<br />

original alert. Additions to the alert can be made using the NAMEBIND EDIT<br />

order. Deletions or other changes to the alert can cause the message to be<br />

unrecognized as an alert by the alert adapters.<br />

v When sending messages to another <strong>NetView</strong> system, the NV option preserves all<br />

message attributes except the cross domain sender name.<br />

v When PPI is used as a requestor, two return codes can be output to the<br />

secondary output stream: the first results from sending the request, the second<br />

from receiving the response. When the send fails, the receive is canceled and<br />

only the return code from the send is passed to the secondary output. When the<br />

receiving session cannot be established, only the receive initialization failure<br />

Chapter 2. Pipeline Stages and Syntax 189

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

Saved successfully!

Ooh no, something went wrong!