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

Syntax<br />

SAFE<br />

►►<br />

SAFE<br />

*<br />

name APPEND<br />

SEIZE<br />

PIPE SAFE<br />

Command Description<br />

A SAFE is a place to store one or more messages associated with a command<br />

procedure. The SAFE stage allows the user to read from or write to a default or<br />

named SAFE. The messages in a SAFE retain their full message structure and<br />

attributes.<br />

If a multiline message created at 08:16:55 and colored red is stored in a safe, then<br />

retrieved and displayed, the displayed message still has the multiline structure,<br />

same time stamp, and is red. Moreover, a DOM that matched the original message<br />

matches the retrieved copy.<br />

The PIPE SAFE stage is similar to the PIPE KEEP stage; PIPE KEEP enables you to<br />

define a task-global place to store messages and PIPE SAFE is a place to store one<br />

or more messages associated with a command procedure. For in<strong>for</strong>mation about<br />

PIPE KEEP stage, see “PIPE KEEP” on page 150.<br />

The types of SAFE are defined as follows:<br />

default SAFE<br />

The current message associated with a command procedure. For example,<br />

when the automation table invokes a command procedure, the default<br />

message is the automated message.<br />

v The default SAFE is preserved as long as the command procedure runs.<br />

v A default SAFE can contain at most one message.<br />

named SAFE<br />

A named area <strong>for</strong> a queue of messages associated with a command<br />

procedure group. For example, a REXX command list can write messages<br />

to a named SAFE, then call a second REXX command list which can read<br />

from, or write to, that named SAFE using the PIPE command.<br />

v A named SAFE is preserved as long as the command procedure group<br />

runs.<br />

v A named SAFE can contain any number of messages.<br />

v A command procedure group can have any number of named SAFEs at<br />

a given time.<br />

When SAFE is a first stage, the specified SAFE is read into the pipeline. For a<br />

named SAFE, this can cause multiple messages to be read into the pipeline.<br />

When SAFE is not a first stage, the input messages are written to the specified<br />

SAFE. For the default SAFE just one message is written and all messages are<br />

copied to the output stream. For a named SAFE, each input message is written to<br />

the SAFE and to the output stream.<br />

►◄<br />

Chapter 2. Pipeline Stages and Syntax 207

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

Saved successfully!

Ooh no, something went wrong!