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

PIPE PPI
192 Programming: Pipes
Notes:
1. The first stage, PPI CNMCOUNT, records the sender's ID as a message
attribute in each message. The attribute is used by the sixth stage, PPI *, to
send the response back to the originator.
2. The EDIT stage in this example can be written with the WRITELINE order to
create a multiline message. Because this example does not assume that the
requestor is another NetView system, it cannot assume that the requestor can
handle a multiline response.
Adding the NV option to the PPI send stage, stage 6, adds the appropriate
multiline identifiers to the data before it is sent to the requestor.
Example: Receiving a Response
In this example a request is sent to a remote PPI receiver running in another
address space. The pipeline then waits for a response.
This example assumes that the remote receiver is another NetView system. Because
it is another NetView system, a multiline response is possible.
/*** issuing a request ********/
address NETVASIS,
’PIPE (NAME PPIOPS)’,
’| PPI OEXXX /egrep "NetView" set.log/’, /*sendrequest ’egrep’*/
’| WAIT 180’, /*wait to 3 min for resp */
| STEM NVnSET.’ /*store response */
Notes:
1. The wait automatically ends when one message is received. This message can
be a multiline message.
2. Multiline identifiers and line descriptors, if any, are removed when the
multiline response is built by PPI processing.
For additional PPI examples, see the following specifications:
v “PIPE EDIT” on page 76
v Example CNMEALUS in DSICLD
v Example CNMEMSUS in DSICLD
v Sample CNMS1101