Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Address space used for exit routine execution z/OS Communications Server: SNA Programming SC27-3674-00 |
|
With a few exceptions, the address space in which an asynchronous
exit routine runs is the ACB address space. The exceptions are:
BIND is always processed by the SCIP exit routine specified in the ACB EXLST; the exit routine runs in the ACB address space. UNBIND processing by an SCIP exit routine (either ACB or NIB EXLST specified) is also done in the ACB address space; if an NIB SCIP exit routine was specified for the session, that exit routine is used, but it runs in the ACB address space and thus might require that the NIB SCIP exit routine be in the operating system's LPA. RECEIVE OPTCD=ANY processing occurs partially in the issuing macroinstruction's address space, partially in the ACB address space, and partially in the address space of the session for which the RECEIVE OPTCD=ANY operation is posted complete (that is, the address space of the session for which input is received). An RPL exit routine can be invoked in either the ACB or session address space. Thus, the application program might need to be written to have such an RPL exit routine in LPA, or to issue RECEIVE OPTCD=ANY only from the ACB address space, and to restrict the sessions that can run in continue-any mode to be those for which the session address space is the ACB address space. LERAD and SYNAD exit routines are normally executed in the address space used by the CHECK or RPL-based macroinstruction for which the LERAD or SYNAD exit routine was invoked. LERAD and SYNAD exit routines for RECEIVE OPTCD=ANY are exceptions in that they can also execute in the ACB address space or the session address space, as well as in the issuing macroinstruction's address space. The program design considerations described for RPL EXIT routines in the preceding paragraph apply also to LERAD and SYNAD exit routines. |
Copyright IBM Corporation 1990, 2014
|