28.11.2012 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PIPE PPI<br />

190 <strong>Programming</strong>: <strong>Pipes</strong><br />

code is returned. See the <strong>IBM</strong> <strong>Tivoli</strong> <strong>NetView</strong> <strong>for</strong> z/<strong>OS</strong> Application Programmer's<br />

Guide <strong>for</strong> more in<strong>for</strong>mation about PPI return codes.<br />

v The PPI stage is not supported under the PPT task.<br />

v When PPI is used as a requestor, the PPI stage chooses a receiver name that is<br />

used to receive a reply. The name chosen is in the <strong>for</strong>m aa#xxxxx where aa is the<br />

system default defined by the PPIPREFX keyword on the DEFAULT command<br />

and xxxxx is a value dynamically chosen at run time. For more in<strong>for</strong>mation<br />

about PPIPREFX, see <strong>IBM</strong> <strong>Tivoli</strong> <strong>NetView</strong> <strong>for</strong> z/<strong>OS</strong> Command Reference Volume 1<br />

(A-N).<br />

If an error is detected in the PPI prefix, a return code is passed to the secondary<br />

stream. If a secondary stream is not defined, message DWO411I is issued with<br />

the incorrect PPI prefix.<br />

v Access to PPI functions can be controlled using SAF or the <strong>NetView</strong> Security<br />

Table.<br />

Security checking is done <strong>for</strong> the pseudo-keywords RECEIVE and SEND on a<br />

DSIPIPPI command. The SEND pseudo-keyword controls both the sender and<br />

requestor functions of PPI.<br />

The SEND and RECEIVE pseudo-keywords correspond to the PPI receiver_name<br />

specified on the PPI stage.<br />

To prohibit using:<br />

PIPE PPI GEORGE | WAIT ...<br />

Code the following PROTECT statement:<br />

PROTECT *.*.DSIPIPPI.RECEIVE.GEORGE<br />

To prohibit using:<br />

PIPE LITERAL /STUFF/ | PPI SAM ...<br />

Code the following PROTECT statement:<br />

PROTECT *.*.DSIPIPPI.SEND.SAM<br />

Return Codes<br />

The following return codes are returned by the PPI stage as signed, 10-digit<br />

decimal numbers:<br />

Return Code Meaning<br />

0 PPI completed successfully.<br />

100 A system abend occurred during a PPI service send or receive. This<br />

might be a <strong>for</strong>ced closure of the PPI address space.<br />

104 A user abend occurred during a PPI service send or receive. See<br />

the <strong>IBM</strong> <strong>Tivoli</strong> <strong>NetView</strong> <strong>for</strong> z/<strong>OS</strong> Application Programmer's Guide <strong>for</strong><br />

more in<strong>for</strong>mation about user abends.<br />

1001 The AIFR or the input length was not valid.<br />

1002 Did not identify the data as a message or MSU.<br />

1003 An incomplete multiline message was discarded by the PPI stage<br />

because of the receipt of an unrelated message from the same<br />

sender.<br />

1004 An illegal alert <strong>for</strong>warding loop was detected. The <strong>NetView</strong><br />

program attempts to avoid loops by not <strong>for</strong>warding alerts back to<br />

their source. Specifically, PPI (TECROUTE) or PPI (TECRTCFM) is<br />

not valid <strong>for</strong> a generic alert whose subvector X'92', flag bit 7, is on

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!