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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PIPE FANOUT<br />

Syntax<br />

FANOUT:<br />

FANOUT<br />

Command Description<br />

The FANOUT stage copies the messages received on its primary input stream to all<br />

connected output streams. Messages copied to the output streams are identical<br />

except:<br />

Streams<br />

v Messages written to the primary output stream retain the IFRAUPRI primary<br />

attribute of the original message. The copy attribute, defined by IFRAUCPY is<br />

set to 0.<br />

v Messages written to all other output streams have the IFRAUPRI primary<br />

attribute setting set to 0 and the copy attribute, defined by IFRAUCPY set to 1.<br />

For more in<strong>for</strong>mation about IFRAUCPY and IFRAUPRI, see <strong>IBM</strong> <strong>Tivoli</strong> <strong>NetView</strong> <strong>for</strong><br />

z/<strong>OS</strong> <strong>Programming</strong>: Assembler.<br />

Stream Type Number Supported<br />

Input 1<br />

Output 10<br />

Termination Conditions<br />

FANOUT ends when the input stream disconnects or all output streams<br />

disconnect.<br />

Operand Descriptions<br />

This stage has no operands.<br />

Usage Notes<br />

Examples<br />

PIPE FANOUT<br />

v The messages are not written to the output streams in any predetermined order.<br />

Streams waiting on input from FANOUT can be delayed.<br />

v If more than 10 output streams are required from FANOUT, one of the output<br />

streams can be used as an input tream to another FANOUT stage. Pass the<br />

primary output stream from the second FANOUT stage to a HOLE stage<br />

because the primary output from the second FANOUT stage does not have a<br />

copy attribute.<br />

Example: Driving Two Different Commands with the Same<br />

Message<br />

In the following example, messages contained in the safe named MYSAFE are<br />

input to FANOUT. The primary output from FANOUT passes the message to<br />

Chapter 2. Pipeline Stages and Syntax 129

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

Saved successfully!

Ooh no, something went wrong!