z/OS Communications Server: SNA Programming
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Procedures to follow in writing exit routines

z/OS Communications Server: SNA Programming
SC27-3674-00

Figure 1 summarizes addressability and save-area requirements for the mainline program and exit routines. In most cases, LERAD and SYNAD exit routines do not have to be reentrant. See Figure 2 for those cases. See Figure 3 for the situations in which exit routines must be reentrant.

Figure 1. Summary of addressability and save-area requirements for the mainline program
The diagram summarizes addressability and save-area requirements for the mainline program and exit routines.
Figure 2. Situations in which LERAD and SYNAD exit routines do not have to be reentrant
The diagram shows situations in which LERAD and SYNAD exit routines do not have to be reentrant. It contains two situations: only the mainline program issues RPL-based requests and only asynchronous exit routines issue RPL-based requests.
Figure 3. Situations in which LERAD and SYNAD exit routines must be reentrant
The diagram shows situations in which LERAD and SYNAD exit routines must be reentrant.
The diagram shows situations in which LERAD and SYNAD exit routines must be reentrant.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014