EPV for MQ provides you with MQ subsystems tuning, MQ applications tuning, daily trends for day-by-day check, weekly and monthly trends for proactive tuning.
MQ subsystems tuning
EPV for MQ Critical Events provides a complete vision of the “health” condition of all MQ subsystems by collecting a set of measures such as storage contractions, logging delays, rollbacks, excessive checkpoints, buffer pool saturation, Coupling Facility structures and SMDS saturation. EPV for MQ Resources analyses the amount of system resources (CPU, storage, virtual storage) used by MQ Address Spaces (Master and Chin), logging activity, checkpoints, Buffer Pool hit ratios and I/O rates, Coupling Facility structures and SMDS activity…
MQ applications tuning
EPV for MQ Workloads provide complete control of all the workloads connecting to each MQ subsystem. Utilizing extensive drill-down capabilities, you can explore workload performance and consumptions by connection type, connection name and transaction. Using EPV for MQ Workloads you can easily eliminate loops and abnormal behaviours, check balancing and perform more effective application tuning activities.
MQ day by day and proactive tuning
EPV for MQ Trends provides daily and monthly critical events, resources, throughput and workload trends. Daily trends will be a key element in day by day tuning activities. By EPV provided functions you can easily compare one day to another and spot anomalies in just few mouse clicks. Monthly trends will assist you in adopting a proactive approach and understand long term tendencies before they can impact your MQ subsystems performance. EPV for MQ also audits Queue Manager parameters and other subsystem definition changes.
Access to available data
EPV for MQ 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.
EPV for MQ 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 EPV Performance database is based on standard SAS files, SQL relational databases or data sets in the Hadoop Distributed File System.
EPV for MQ 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.
EPV for MQ can also run on top of SAS. In this case the requirements are:
• Availability of a SAS System Base module at least on a PC;
• Availability of one of the following products: SAS ITRM, MXG.