Raw monitor data is only the starting point, XM offers the solution

DB2 databases are constantly being modified by a multitude of applications. Utilities re-organize, check and backup data, while updates are taking place in real time. z/OS activities generate system level messages at the same time that DB2 logs information about itself. Messages, warnings and problem descriptions quickly become both massive and unmanageable. Great effort is required to view and evaluate this flood of information. Filtering out the relevant items from this high volume of raw data is a major task. It is not enough to scan for specific messages or to analyze the output of a number of display commands. Early problem detection, and the avoidance of costly disruptions, requires that an intelligent analytical engine draw timely conclusions from several different data sources.

Today there are several monitors for DB2 and z/OS on the market that provide excellent raw statistics. However, they all lack an analytical engine to convert that raw data into useful information. The ability to determine when a true exception (error) situation exists is unique to XM. It automatically tracks suspicious and potentially harmful events, alerts accountable staff and can even take predetermined solution steps. The primary purpose of the legacy monitors is to provide data for the local expert to analyze, and if the DB2 subsystem is ailing guess whose job it is find the problem before it impacts the users. Today’s non-stop environments and stringent SLA’s require more than a passive legacy monitor can deliver.

XM4DB2 was designed to facilitate the operations and production DBA staff’s pro-active management of DB2 subsystems. It provides predefined solutions and is also flexible enough to allow for customized exception handling. Recurring exceptions that lead to specific errors, and which may seem to be unavoidable with in-house standards, need special handling.  XM4DB2 supports user-defined actions, including commands and/or prepared jobs that implement a specific remedy and alerts. The actions can be reviewed or supplemented by the staff prior to submission for execution. Full automation allows direct submission by XM, passing jobs to a scheduler or a data maintenance system, such as, UBS’ TUC product.

XM does not overwhelm the staff with the senseless repetitive reporting of known problems. Instead, it tracks a detected problem and removes it from the exceptions list as soon it is resolved.  The exception is logged in the historical exceptions list for future statistical analysis and for knowledge base referencing.

XM is of great value to DB2 shops that wish to maintain high service levels with minimal interruptions to their production environments.