z/OS MVS Programming: Workload Management Services
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


Exit Routine Environment

z/OS MVS Programming: Workload Management Services
SC34-2663-00

Exit Routine Environment

The server connect exit routine receives control in the following environment:

Authorization:Supervisor state key 0
Dispatchable unit mode:SRB
Cross-memory mode:PASN=HASN=SASN with the current home address space the same as when the server issued the IWM4CON macro instruction.
AMODE:31-bit
ASC mode:Primary
Interrupt status:Enabled for I/O and external interrupts
Locks:No locks held
SerializationIt is possible for the exit to be called before the caller has received control back from IWM4CON. The exit or any program it drives (synchronously or asynchronously) must synchronize with the program issuing IWM4CON to ensure that IWM4CON has returned a connect token prior to issuing IWM4DIS (disconnect) or any other service that requires the connect token.
LocationThe server exit must be a resident routine callable from the server address space and must remain available after the server manager disconnects or after the termination of the server task which issued the IWM4CON. The exit need not persist after termination of the server address space.

The input parameter list is in pageable storage addressable in the primary address space, but should not be changed by the exit.

Exit RecoveryThe system may cause the server to become ineligible to be recommended by IWMSRFSV (find server) if there have been repetitive errors in calling the exit. The exit may optionally establish a functional recovery routine (FRR) or ESTAEX for any needed recovery or cleanup of its resources.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014