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

PIPE CORRWAIT
processing until the stage at the remote NetView system completed. At that point,
the NetView stage disconnects and CORRWAIT ends with its input stream
disconnected.
CORRWAIT processing is the same when more than one command is issued by the
preceding stage. For example, if you create a stem variable containing a series of
LIST DST= commands for all your DSTs and then issue:
PIPE STEM LISTCMDS.|NETVIEW|CORRWAIT 20| ...
Each LIST stage queues a request for data to a DST and ends, but CORRWAIT
continues to wait until each of the queued requests completes.
Notification support to CORRWAIT is not available for many VTAM and MVS
commands. Because this support is not available, these commands are considered
never-ending. CORRCMD and CCDEF can be used to handle VTAM and MVS
commands.
You can define a secondary output for CORRWAIT if you want CORRWAIT to
process in a different manner. CORRWAIT produces a message on its secondary
output stream each time a completion event occurs. When a secondary output
stream is defined, CORRWAIT continues to wait only while the secondary output
stream remains connected.
The messages passed to the secondary output stream consist of a plus or minus
sign followed by a 10-character, right-aligned-, zero-padded completion code. This
completion code is followed, beginning in position 13, by information which might
be useful in debugging your pipeline. The debugging information includes:
v The domain ID where the event occurred
v TVBOPID where the event occurred
v The command completing, if applicable
Attention: Domain ID, TVBOPID, and the command completing are not intended
as a programming interface, because formats might change and additional data
might be included in the future. Use these only for problem determination.
The completion codes are based on the type of event, not the return code from a
command.
Completion Code
Event
+0000000000 A command thread completed (see note).
+0000000008 A timeout occurred.
+0000000012 A GO command was issued.
+0000000016 A task executing a thread terminated.
+0000000032 An ABEND occurred on a task that was executing a thread.
−0000000005 A RESET occurred on a remote task that was executing a thread.
Note: A command thread is any command executing under the control of the
pipeline or any secondary command created or queued by such a command.
When secondary commands create additional commands, these are not
counted individually, rather, the completion of the last secondary command
is reported as the completion of its parent secondary event.
Chapter 2. Pipeline Stages and Syntax 55