IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

PIPE CORRWAIT
58 Programming: Pipes
examine the incoming messages one at a time and can create a named SAFE, if
necessary. Like the DROP stage in this example, your procedure can produce a
message to drive PIPEND when it is appropriate to end the wait.
Example: Early timeout following an expected message flow
This pipe waits three seconds for responses to begin and one second following any
(unexpected) single-line message(s). Following receipt of an MLWTO (the expected
IEE114I), it times out immediately.
PIPE MVS D A,L | WAIT 3 10 0 | CONS
Example: Using a Secondary Output Stream with CORRWAIT
CORRWAIT can be coded to end when one of the following situations occurs:
v 60 seconds has elapsed.
v The operator entered the GO command.
v A task end or ABENDS.
For CORRWAIT to process in this manner, include the following statements in
your pipeline specification:
...
|A: CORRWAIT 60
...
%
A:
|NLOCATE 1.11 /+0000000000/
|TAKE 1
|HOLE
...
Assuming that the pipeline end character was defined as a %, the simple pipeline
after the A: connector processes the secondary output stream from CORRWAIT 60.
If a completion code other than +0000000000 is processed, CORRWAIT terminates.