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

PIPE CORRWAIT
56 Programming: Pipes
Operand Descriptions
interval
Specifies the maximum time, in seconds, between messages before messages
are no longer collected. Valid values are in the range of 1 - 10,000,000. The
default is 1.
An asterisk (*) can be specified for interval. When an asterisk is specified,
CORRWAIT never times out. The following conditions end the wait:
v A GO command
v A RESET command
v A PIPEND pipe stage
v Secondary output disconnect
v Other conditions that end a wait
seqWait
The second number (after interval) specifies the time in tenths of a second to
wait between messages, after the first message. This is to allow the timeout to
change after responses have begun to flow. Valid values are in the range of 0 -
10,000,000. The default is the same time period (ten times the value of the
argument) as the interval. Note that, for purposes of determining the "first"
message, command echos are ignored, as are certain (unseen) internal NetView
flows.
aftMlWait
The third number (after seqWait) specifies the time in tenths of a second to
wait following receipt of the first multi-line message. This allows you to
change the wait period when you know the pattern of responses. Valid values
are in the range of 0 - 10,000,000. The default is the same time period as was
specified for the seqWait.
MOE
Usage Notes
Message on error (MOE) inserts message DWO369I containing a return code
into the stream when a timeout occurs, after any messages the command might
have returned.
CORRWAIT recognizes an artificial timeout if the operator enters the GO
command while the wait is in effect.
v The display of W in the upper right of the operator's screen indicates that
CORRWAIT is actively waiting for messages.
v Another stage must follow CORRWAIT in order to actually wait for a specific
interval of time.
v When routing a PIPE command to another domain (using RMTCMD), ensure
that your CORRWAIT values are long enough. The system discards
asynchronous, correlated messages that arrive after a CORRWAIT times out.
v When a terminating stage (TOSTRING or TAKE) is used to end a wait, the
terminating stage must immediately follow CORRWAIT. This applies only to
MVS or VTAM commands, because NetView commands automatically end
CORRWAIT when the commands end.
v For performance considerations when issuing a command to MVS or VTAM, use
a stage containing terminating conditions (for example, TOSTRING or TAKE
FIRST) after a CORRWAIT stage. Terminating conditions end data streams early
in the pipeline and allow the pipeline to end before the timeout period.