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

Debugging NetView Pipelines
Clogged Pipelines
346 Programming: Pipes
Complex pipelines with multiple data streams can become deadlocked or clogged.
Clogs are caused by errors in the structure of the data stream connections.
In a clogged pipeline one stage requires data from another and this data cannot be
provided. All pipeline processing stops.
A clog occurs when either:
v A stage needs to give data to another stage that cannot receive the data.
v A stage needs to get data from another stage that cannot provide the data.
The following example creates a clogged pipeline, because it attempts to read a
file, convert the last two lines into label lines, and collect all the lines into a
multiline message.
/* REXX Fragment */
...
’PIPE (NAME CLOGGER END \)’,
’|