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.

Chapter 3. <strong>NetView</strong> Pipelines Device Drivers<br />

This chapter documents general-use programming interface and associated<br />

guidance in<strong>for</strong>mation. For in<strong>for</strong>mation about using pipelines in high-level<br />

languages, see <strong>IBM</strong> <strong>Tivoli</strong> <strong>NetView</strong> <strong>for</strong> z/<strong>OS</strong> <strong>Programming</strong>: PL/I and C.<br />

Device drivers are stages that move data between your pipeline and other system<br />

resources (such as command procedure variables, DASD, keyboards, displays, and<br />

so on).<br />

When using drivers that can be placed anywhere in a pipeline (such as, STEM,<br />

VAR, and SAFE) be aware that they work differently depending on where they are<br />

placed. When first in a pipeline, these device drivers read from the system<br />

resource. When used anywhere else in the pipeline, they write to the system<br />

resource, often replacing existing data.<br />

Attention: You can overwrite or destroy data when you misplace these device<br />

drivers.<br />

Interfacing with the Task: CONSOLE, HELDMSG, LITERAL, LOGTO<br />

This section describes several device drivers that interface with the task. You can:<br />

v Display pipeline contents on the screen (CONSOLE)<br />

v Route pipeline contents to another pipeline (CONSOLE)<br />

v Copy held messages from your operator console (HELDMSG)<br />

v Insert text into the pipeline (LITERAL)<br />

v Copy pipeline contents to a specified log (LOGTO)<br />

Displaying Messages: CONSOLE<br />

The CONSOLE stage enables the user to:<br />

v Display messages on the screen while these messages remain in the pipeline <strong>for</strong><br />

use by the next stage.<br />

v Remove the status of held messages that are in the pipeline be<strong>for</strong>e rewriting<br />

them on the screen (using the DELETE option).<br />

v Return messages to its caller (without displaying the messages), when it is a<br />

stage of the inner pipeline as part of a PIPE-within-a-PIPE structure.<br />

Example 1: Displaying Results While Avoiding Logging<br />

This example shows how to use the CONSOLE stage with the ONLY option to<br />

display messages in the pipeline without logging or exposing the messages:<br />

PIPE NETVIEW LIST ’’ | CONSOLE ONLY<br />

Output from the pipeline follows:<br />

© Copyright <strong>IBM</strong> Corp. 1997, 2011 283

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

Saved successfully!

Ooh no, something went wrong!