Exception processing exit

Exception processing exits are user exits that handle periodic exceptions and event exceptions.

You can activate or deactivate exception processing exits from the Exception Processor panel with the Host Online Monitor (as described in IBM® Db2® for z/OS® in IBM Documentation) or from the Exception Processing window with the Workstation Online Monitor.

The exception processing exit is implemented as an asynchronous task. It is provided as a load module named DGOMEPXT, which contains the modules DGOMEPXT, DGOMUPXT, and DGOVQUEU.

Module DGOMEPXT is posted whenever the periodic exception task or the event exception task detects an exception condition. It receives the queued exception log file records using the services of module DGOVQUEU and calls the user exit routine DGOMUPXT.

In RKO2SAMP, OMEGAMON for Db2 PE provides a sample of the exception processing exit, called DGOMUPXT, which issues a message to the operator. The message text varies depending on whether the situation is an event exception or a periodic exception. For a description of the different formats of this message, see message number DGOV0100I in Messages.

You can change DGOMUPXT according to your needs, for example, to examine the type of exception and perform an action necessary to handle the situation.

The exception processing exit runs in the Data Collector address space as a subfunction of periodic exception processing. Therefore, the exit remains active even if the administrator exits OMEGAMON for Db2 PE for as long as periodic exception processing remains active in the Data Collector address space.