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.

– Output from the stage is collected into a single multiline message <strong>for</strong><br />

cross-domain transfer.<br />

v At the local domain:<br />

– The local wait is terminated when the response is received.<br />

– Results are displayed on the screen.<br />

Example: Issuing Multiple Commands at a Remote Domain<br />

By coding a label as the only argument of CORRCMD you can execute multiple<br />

stages at a remote domain. Commands are passed on the input stream. For<br />

example the following stages executes each stage stored in the stem SOMECMDS.<br />

and stores all the responses from the stages in the RESPONSES. stem:<br />

PIPE STEM SOMECMDS. | CORRCMD CNM02: | STEM RESPONSES.<br />

Example: Routing Commands and Data to a Remote Domain<br />

through an Autotask<br />

In this example the data contained in the stem MYDATA. is sent to the remote<br />

domain CNM02 where it is used by the USEDAT stage. The remote stage<br />

conversation is also shared with others by using the RMT02 autotask. The stage,<br />

with the data, is routed first to the autotask and then to the remote domain.<br />

’PIPE (NAME DBL_HOP)’,<br />

’| STEM MYDATA.’,<br />

’| CC /RMT02: CNM02: USEDAT’,<br />

’| STEM RESPONSES.’<br />

PIPE CORRCMD<br />

Output from USEDAT is routed back through the same path used to send the<br />

stage.<br />

Chapter 2. Pipeline Stages and Syntax 53

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

Saved successfully!

Ooh no, something went wrong!