0

The PPI request has completed successfully. The requested function has been performed with no errors or warnings.

3, 4, 9, 12, 14, 22, 24, and 60

4

The specified receiver is not presently active. The data buffer or generic alert has been queued. (The receiver buffer queue was not full).

12 and 14

10

The PPI facility is active and can be used. This return code is good.

1

14

The receiver program is active.

2

15

The receiver program is (already) inactive. The program is defined, but has been explicitly or implicitly deactivated.

2 and 9

16

The receiver program is already active. The program cannot be defined.

4

18

The ECB is not 0 (normally the receiver ECB). This condition is not necessarily an error because the ECB can be posted after it was last checked.

24

20

Request type is invalid. The passed request code was not valid. This condition can occur with request code 60 if this product is not providing the PPI. Otherwise, it is probably an error in formatting of the RPB.

Any incorrect request

22

The program is not executing in primary addressing mode. Programs must not call the PPI in secondary mode (z/OS). They must be in primary mode, although they can be in cross-memory mode (that is primary ^= home).

1, 2, 3, 4, 9, 12, 14, 22, 24, and 60

23

The program is not authorized. Attempt to send a buffer to a receiver defined as authorized.

14

24

PPI is not active. The SSI is not active or PPI is not running on a SOLVE SSI or Tivoli NetView SSI. In this product's implementation, can also indicate that this system does not support PPI, as it has not built the relevant control block structure.

All

25

The ASCB address is not correct. To deactivate a receiver or receive data, the correct ASCB address must be supplied.

9 and 22

26

The receiver is not defined. The supplied receiver name has never been defined to this execution of PPI.

Note: This condition could occur if the PPI-owning SSI is stopped and restarted.

2, 9, 12, 14, and 22

28

This product does not support PPI. This return code cannot occur with the implementation of the SOLVE PPI. It can occur if Tivoli NetView is providing PPI services.

All

30

No data buffers are available in the receiver queue. There is no data to be received. PPI clears the receiver ECB automatically.

22

31

The receiver data buffer length is too short to receive the next data buffer. The RPB buffer length contains the length of the pending buffer.

22

32

No storage available. Unable to obtain storage required to complete the requested function.

4, 12, and 14

33

Invalid buffer length. The supplied RPB or data buffer length was not valid. For a data buffer, the length must be less than 1 or greater than the PPI maximum buffer size JCL parameter.

All

35

The receiver buffer queue is full. As the queue is full, the new data buffer is not added to the queue.

12 and 14

36

Unable to establish ESTAE protection as requested. Either the caller is not in home mode, or the ESTAE gave a nonzero return code.

All

40

The specified receiver or sender ID is invalid. The value does not satisfy the documented rules for these IDs, or (when defining, deactivating, or receiving for a receiver), starts with NETV or NETM and the requesting task is not the SSI-connected product region.

4, 9, 12, 14, and 22

90

A processing error has occurred. This return code is a catch-all that covers many things:

• ESTAE-trapped ABENDs
• Various internal errors

All