Exit 22 – NOTIFY Driver Note Selection
Use Exit 22 to determine if a NOTIFY link driver should create and issue a note when a file is queued on the link.
Point of Processing
| Process | Exit Attribute |
|---|---|
| NOTIFY link driver | Reentrant |
Exit 22 is called when a file is queued on a NOTIFY-type link. RSCS has not yet issued a note.
On return, if your exit routine issues return code 0 or 4, RSCS generates a note. The contents and destination of the note are specified by the TEMPLATE file with which the NOTIFY-type link was initialized.
Entry Conditions
The following table shows the parameters passed in R0 and R1 to the first exit routine associated with this exit point. For more information about other register contents, see Standard Entry Conditions.
| Register | Contents |
|---|---|
| R0 | Not applicable |
| R1 | Address of a parameter list that contains:
|
Exit Conditions
On return, Exit 22 sets the standard register contents (see Standard Exit Conditions).
Return Codes
| Return Code | Results |
|---|---|
| 0 | RSCS calls the next exit routine associated with this exit point and continues usual processing. |
| 4 | RSCS does not call any other exit routines associated with this exit point and continues usual processing. |
| 8 | RSCS purges the misdirected file and sends a message to the file originator. |
| 12 | RSCS calls Exit 23 to modify the note sent to the file originator. |
| 16 | RSCS holds the file on the NOTIFY-type link but does not send a note to the file originator. |
Programming Considerations
- To communicate between Exit 22 and Exit 23, your exit routine should use the NOTEUSER field in the NOTEBLOK.