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

PIPE ROUTE<br />

Syntax<br />

ROUTE:<br />

ROUTE<br />

label:<br />

AUTHRCVR<br />

BULLETIN<br />

Command Description<br />

The ROUTE stage sends messages to another task. The target task is identified by a<br />

standard <strong>NetView</strong> label or by the authorized receiver (AUTHRCVR), as specified<br />

by the previous ASSIGN command.<br />

Streams<br />

204 <strong>Programming</strong>: <strong>Pipes</strong><br />

If you use the label syntax, the target task can be local (in the same <strong>NetView</strong><br />

program) or remote (in another <strong>NetView</strong> program). For a remote target, the<br />

message is routed similarly to a RMTCMD response by SNA or by TCP/IP,<br />

depending on the domain name. For more in<strong>for</strong>mation on the domain name<br />

specification, see the RMTSYN statement in the CNMSTYLE member.<br />

If an argument is not specified, ROUTE reads target specifications from the<br />

secondary input. One message is read from the secondary input <strong>for</strong> each message<br />

routed. If the message read from the secondary has multiple lines, a single<br />

message from the primary stream is routed to each target specified.<br />

The message is also written to an output stream under the following conditions:<br />

v If the routing is successful, the message is written to the primary output stream,<br />

if connected.<br />

v If the routing is not successful, the message is written to the secondary output, if<br />

defined and connected. If no secondary output was defined, the message is<br />

written to the primary output, if connected.<br />

Note: When multiple targets are specified, the operation is regarded as successful<br />

if any one of the message routings is successful. For a remote target, the<br />

routing is successful if SNA or IP routing methods accept the message <strong>for</strong><br />

routing. A subsequent failure (<strong>for</strong> example the domain is inactive or security<br />

prevents the session from being established), is reported by messages to the<br />

authorized receiver.<br />

Stream Type Number Supported<br />

Input 2<br />

Output 2<br />

Termination Conditions<br />

ROUTE terminates when the primary input stream disconnects.

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

Saved successfully!

Ooh no, something went wrong!