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

PIPE PPI
Streams
188 Programming: Pipes
When acting as a requestor, follow the PPI with CORRWAIT with a sufficient wait
time for the response to be returned. PPI automatically ends the wait when one
message is received. This message can be a multiline message.
The PPI stage, unlike other NetView PPI receivers, can receive multiline messages.
Multiline messages must be in a specific format to be recognized by the NetView
program:
v The message must be prefixed with a seven character multiline identifier and a
one-character line descriptor. The multiline identifier must be
X'0F0DC4E2C9FFE3'. The line descriptor indicates the line type desired along
with whether line attributes are provided.
v Line type must be one of the following types:
C Control line
L Label line
D Data line
E End line (can contain data)
Note: The first line must be a control line.
Stream Type Number Supported
Input 1
Output 2
Termination Conditions
PPI terminates when the input stream disconnects or if the secondary output
stream disconnects, if defined.
An input stream can only be specified when PPI is used as a sender. Input
messages are copied to the primary output stream if the primary stream is
connected.
When PPI is used as a receiver or requestor, received messages are written to the
output stream. These messages are identified by a sender message attribute if a
sender name is provided. This sender name is the sender field IFRAUSDR.
A signed 10-digit decimal return code is written to the secondary output stream if
the secondary stream is connected.
Operand Descriptions
receiver_name
A one-to-eight character name of the PPI receiver.
When PPI is a sender or requestor, receiver_name is the name of the program
receiving the sent messages. The abbreviation *ALERT means the alert receiver
name defined to the NetView program.
When PPI is a receiver, receiver_name is the name that is used by other
programs to communicate with the PPI stage.