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

PIPE PPI
Syntax
PPI Sender:
PPI
PPI Receiver:
(DATAONLY)
(TECROUTE)
(TECRTCFM)
(TRAPROUT)
(MLWTO)
(NV)
receiver_name
*
PPI receiver_name
(APONLY)
PPI Requestor:
PPI receiver_name /string/
(APONLY)
Command Description
The program-to-program interface (PPI) stage communicates with another address
space in the same host using the NetView program-to-program interface. PPI can
be used in three ways:
v Sender
v Receiver
v Requestor
When PPI has an input stream, PPI acts as a sender. The data received on the
input stream is passed to the receiver specified by receiver_name.
If PPI does not have an input stream, PPI acts as a receiver. The receiver_name
specifies the name where data must be sent to be processed by the PPI stage.
PIPE PPI
When acting as a receiver, follow the PPI with CORRWAIT * so data can be received
continuously without deactivating the receiver. If the receiver is deactivated, even
for a short time, senders might encounter errors.
Note: When PPI is used as a receiver, the pipe option LOWQENAB is in effect
even if not explicitly specified. See “PIPE (NCCF) ” on page 20 for more
information about LOWQENAB.
When a /string/ is specified, PPI acts as a requestor. The /string/ is sent to the
receiver specified by receiver_name and PPI waits for a response. A receiver name is
automatically generated to receive the response.
Chapter 2. Pipeline Stages and Syntax 187