z/OS UNIX System Services Planning
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Using installation exits

z/OS UNIX System Services Planning
GA32-0884-00

You can use installation exits to enable applications to monitor process activities.
Preprocess initiation exit (BPX_PREPROC_INIT)
Receives control immediately before the creation of any new process. This exit cannot use any z/OS UNIX callable service. When these exit routines receive control, the Process Exit Data Block (PEDB) will contain data about the creating process.
Post-process initiation exit (BPX_POSPROC_INIT)
Receives control immediately after the creation of any new process. When this exit receives control, the Process Exit Data Block (PEDB) will contain the creator and the new process data.
Process image initiation exit (BPX_IMAGE_INIT)
Receives control immediately before any new process image is initiated. This occurs after a successful spawn, attach_exec, attach_execmvs, exec, or execmvs callable service is done. The exit will receive control before the new process image file is run. When this exit receives control, the Process Exit Data Block (PEDB) will contain the data of the creator and the new image.
Preprocess termination exit (BPX_PREPROC_TERM)
Receives control immediately before the termination of a process. These exits might receive control in the address space of the process or in the master address space, if the address space of the process was terminated. In the latter case (ASID=1), the exit cannot use z/OS UNIX callable services. When these exits receive control, the Process Exit Data Block (PEDB) will contain details about the terminating process.
Exit routines can be added to each exit point. z/OS UNIX passes control to the exit routine when an exit point is reached. Information about the current process and its creator is then passed to the exit routine.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014