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

Additional Troubleshooting Tips
Debugging NetView Pipelines
If you are not getting the output you expect from your pipeline, check for these
possible causes:
v The HOLE stage is discarding all pipeline messages.
v The CORRWAIT stage is not used following a command-executing stage, such as
NETVIEW or VTAM, causing asynchronous messages to be lost because no time
interval is allowed for their return.
v Pipeline messages are not generated by the stage preceding the NETVIEW stage;
therefore, the command issued by the NETVIEW stage is not triggered to
execute.
v In a PIPE-within-a-PIPE structure, the CORRWAIT stage is not used, or is used
incorrectly, following the CONSOLE stage, which is used to return messages
from a remote pipeline to a local pipeline. The function of the CORRWAIT in the
local pipeline is to wait for messages to travel from the remote to the local
NetView. The CORRWAIT stage must be used. If it is already being used
increase the interval. In addition, you might want to add the MOE option to
check for a timeout. There must be enough time allowed for the messages to
travel from the remote to the local NetView.
v You have multiple pipelines in a command list or a PIPE-within-a-PIPE
structure, but you have not used the NAME option to distinguish them.
Chapter 8. Debugging NetView Pipelines 351