Send a Generic Alert

To send a generic alert, use request code 12. No special PPI setup is required.

The RPB fields in the following table must be set up before the call:

Bytes	Field Name	Set to...
00–03	RPLEN	56.
04–05	REQUEST	12.
06–07	RECOPT	A recovery option as required.
12–15	WORKADDR	The address of a 128-byte work area.
32–35	BUFFLEN	The length of the generic alert data.
36–39	BUFFADDR	The address of the generic alert data.

The RPB field in the following table is returned after the call:

Bytes	Field Name	Set to...
08–11	RETCODE	The return code.

The following return codes are possible:

0: Request completed successfully.
4: The ALERT receiver task (NETVALERT) is not active—the alert has been queued.
22: The requestor is not in primary addressing mode.
24: PPI is not active.
26: The NETVALERT receiver program is not defined.
28: PPI requests are not supported.
32: No storage is available.
33: The buffer length is invalid.
35: Alert receiver buffer queue is full.
36: ESTAE could not be established as requested.
40: Sender ID is invalid.
90: A processing error occurred.

Note: The generic alert must include the 8-byte NMVT header.

The default buffer queue limit for the alert receiver is 1000 generic alerts.

A return code of 22 or greater means that the alert has not been copied to the alert receiver queue.

If no hierarchy or resource list subvector is provided in the generic alert, the sender ID is used as the resource name.

PPI does not release the data buffer storage. Your program must release storage if necessary.