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.

Emptying the Pipeline: HOLE<br />

NCCF NETVIEW CNM01 OPER6 03/26/10 09:02:44<br />

* CNM01 DROP2<br />

’ CNM01<br />

IST350I DISPLAY TYPE = MAJOR NODES<br />

IST089I VTAMSEG TYPE = APPL SEGMENT , ACTIV<br />

IST089I A01MPU TYPE = PU T4/5 MAJ NODE , ACTIV<br />

IST089I ISTPDILU TYPE = CDRSC SEGMENT , ACTIV<br />

IST089I ISTCDRDY TYPE = CDRSC SEGMENT , ACTIV<br />

IST089I A01APPLS TYPE = APPL SEGMENT , ACTIV<br />

IST089I A01MVS TYPE = APPL SEGMENT , ACTIV<br />

IST089I A01USER TYPE = APPL SEGMENT , ACTIV<br />

IST089I A01CDRM TYPE = CDRM SEGMENT , ACTIV<br />

IST089I A01CDRSC TYPE = CDRSC SEGMENT , ACTIV<br />

IST089I A01LOCAL TYPE = LCL 3270 MAJ NODE, ACTIV<br />

IST314I END<br />

C CNM01 RETURN CODE IS 0<br />

Processing steps:<br />

1. The NETVIEW stage runs the MAJNODES command list. Usually, this displays<br />

active major nodes in a domain on your console. When the command list is<br />

issued within a pipe, the output messages are placed in the pipeline.<br />

2. The CORRWAIT stage allows a 10-second wait <strong>for</strong> messages to be returned<br />

from VTAM.<br />

3. Be<strong>for</strong>e the 10 seconds expire, the message DISPLAY NET MAJNODES returns to the<br />

pipeline and is passed to the next stage. The DROP stage reads its input stream<br />

and discards the message.<br />

4. Again, be<strong>for</strong>e the 10 seconds expire, the second message DISPLAY ACCEPTED<br />

returns to the pipeline, is read, and discarded by the DROP stage.<br />

5. Again, be<strong>for</strong>e the 10 seconds expire, the MLWTO is passed to DROP, and<br />

because DROP has reached its maximum discard count, the MLWTO is<br />

preserved in the pipeline.<br />

6. The CONSOLE stage reads the messages and displays them.<br />

This section describes how to discard all messages from the pipeline, thus<br />

emptying it of all contents.<br />

Determining Correlation: HOLE<br />

Discarded messages from the pipeline Using the HOLE stage, you can, <strong>for</strong><br />

instance, empty the pipeline of messages after writing them to a variable or to test<br />

a command <strong>for</strong> correlated output.<br />

Example: Determining Command Response Correlation to a Command<br />

This example shows how to use the HOLE stage to determine whether a command<br />

and its messages are correlated. If the messages are correlated, they enter the<br />

pipeline and are discarded; otherwise, they are displayed.<br />

PIPE NETVIEW MVS $D I | CORRWAIT 25 | HOLE<br />

Output (first page only) from the command looks similar to:<br />

<strong>NetView</strong> Pipeline Filters<br />

Note: These messages represent uncorrelated messages, indicating that the<br />

command is NOT supported <strong>for</strong> pipeline processing. They displayed<br />

immediately after the PIPE command was entered.<br />

Chapter 4. <strong>NetView</strong> Pipeline Filters 313

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

Saved successfully!

Ooh no, something went wrong!