Detect Problems Before Your Users Do
XM4DB2 continuously inspects each mission critical Db2 system. It proactively looks for indicators for current or potential future problems, so called ’exceptions‘. An exception is an unacceptable situation that Db2 or another z/OS component cannot automatically solve. XM4DB2 alerts DBA staff and optionally can take action to rectify the situation. Working in the background it continually checks for availability of Db2 objects and the operational readiness of utilities, plans and packages.
The XM4DB2 environment
XM4DB2 consists of three parts, the observer collecting and processing exceptions, the ISPF user interface managing parameters and displaying exceptions, and optionally the director building the connection between different observers and the single point of control. The observer has to be installed once on each LPAR where Db2 subsystems should be supervised. It can observe any number of Db2 subsystems running on an LPAR. The connection to the director is done via TCP/IP.