DB2 subsystems tuning
EPV for DB2 Critical Events provides a complete vision of the “health” condition of all DB2 subsystems by collecting a set of measures such as: logging delays, thread and RID pool failures, buffer pool and global buffer pool internal thresholds violations …
EPV for DB2 Resources analyses the amount of system resources used by DB2 Address Spaces (Master, DBM1, IRLM, DIST and Stored Procedures), deadlock and timeout events up to the impacted applications, DBD and EDM pool usage, Buffer and Global Buffer Pools hit ratios and read rates …

DB2 applications tuning
EPV for DB2 Workload provides complete control of all the workloads connecting to each DB2 subsystem. Utilizing extensive drill-down capabilities, you can explore workload performance and consumption at the connection type, plan, authid, correlation id, plan and package level.
Using EPV for DB2 Workload you can easily eliminate loops and abnormal behaviours, check sysplex balancing and perform more effective application tuning activities

DB2 day by day check and proactive tuning
EPV for DB2 Trends provides daily, weekly and monthly critical events, resources, throughput and workload trends.
Daily trends allow performing a daily check of even complex environments in minutes. By using EPV provided functions you can easily compare one day to another and spot anomalies in just few mouse clicks.
Weekly and monthly trends will assist you in adopting a proactive approach and understand long term tendencies before they can impact your DB2 subsystems performance.
EPV for DB2 also audits DSNZPARM and other subsystem definition changes.

Access to available data
EPV for DB2 uses standard measures normally available in the z/OS environments and supports various sources, such as ITRM (IT Resource Management), MXG (Merrill’s eXpanded Guide) or native SMF data.

Using “de facto” Standard Technologies
All reports are produced in simple static HTML pages published on a server of your choice and can be accessed by your favourite “browser”. All the tables provided in the reports can be exported individually or together in a MS-Excel spread sheet.

Architecture
EPV for DB2 architecture is based on the following three layers:
• An interface to collect input data
• An engine to correlate and aggregate data
• An engine to produce HTML pages.

The interface to collect input data is designed to optimize performance and consumptions of the loading phase, avoiding duplication or loss of data. It uses simple exits that adapt the product to the environment characteristics; a set of ready exits for each data type to acquire is provided.

The engine to correlate and aggregate data builds a standard SAS or SQL relational Data Base, containing only those metrics used by the product and automatically aggregated at the monthly, daily and hourly level. You can customize the product by setting the appropriate parameters and values to keep in your EPV Performance Data Base the desired time periods.

The engine to produce the HTML pages can be customized to:
• Report daily resource and workload statistics for any desired period
• Report daily weekly and monthly trends for any desired period
• Report top consumers in DB2 by connection type (batch, CICS, DDF, IMS, TSO, WEBSPHERE, etc.)
• and much more…

Requirements
EPV for DB2 is available in two modes: standard or Plus.

The requirements for EPV for DB2 are:
• Availability of a SAS System Base module at least on a PC
• Availability of one of the following products: SAS ITRM, MXG.
EPV for DB2 Plus has no pre-requisites; it’s an “out of the box” solution which integrates a light version of the EPV zParser product to interpret the needed SMF records and all the other input data required.