Getting the Most out of zEDC Hardware Compression


By Todd Havekost

One of the challenges our customers tell us they face with their existing SMF reporting is keeping up with emerging z/OS technologies. Whenever a new element is introduced in the z infrastructure, IBM adds raw instrumentation for it to SMF. This is of course very valuable, but the existing SMF reporting toolset, often a custom SAS-based program, subsequently needs to be enhanced to support these new SMF metrics in order to properly manage the new technology.

z Enterprise Data Compression (zEDC) is one of those emerging that is rapidly gaining traction with many of our customers, and for good reasons:

  • It is relatively straightforward and inexpensive to implement.
  • It can be leveraged by numerous widely used access methods and products.
  • It reduces disk storage requirements and I/O elapsed times by delivering good compression ratios.
  • The CPU cost is very minimal since almost all the processing is offloaded to the hardware.

A New Infrastructure Component to Manage

If you are implementing zEDC, these cards represent a new component in your infrastructure that must be managed to ensure sufficient capacity and consistent performance. The benefit of this is that it interprets and combines all the information in the SMF and RMF records, connecting the hardware view from the zEDC records with the SMF job records. It also provides a comprehensive set of reports out of the box. This gives you the visibility you need to effectively manage zEDC, along with all the other critical aspects of your z/OS infrastructure, without requiring any programming.

Visibility into Important Metrics

One metric of immediate interest for zEDC and other PCIe cards is the card utilization. This is essential to ensure the number of configured cards provides sufficient capacity to process the volume of compression activity in your environment without introducing delays that could impact the entire I/O infrastructure.
Utilization for all hardware accelerators

IntelliMagic Vision applies z/OS specific expert knowledge to key metrics to identify issues requiring attention before they impact production workloads. Rated metrics for PCIe cards like zEDC include service times and queue times, providing early warning when service is beginning to deteriorate.

hardware accelerator service time

What Compression Ratio Are We Achieving with zEDC?

One of the first questions about zEDC you are likely to be asked by management is “what compression ratio are we achieving?”

compression ratio for compress requests

In the example above, compression ratios were typically 6:1 or better, but there was an interval around 5 pm when the ratio for one of the processors (CEC-B in blue) dipped to 1:1. This is a particularly powerful example of how the flexible drilldown capabilities all the way from the hardware perspective to the job level helped analyzing the problem. Drilling down on the data by system and ultimately by address space displayed the jobs executing at the time of the low compression ratio, see table below. Armed with the information that one job was the dominant user of compression at that time, issuing well over 700,000 requests, an informed decision could be made whether the data being accessed by that job warranted being compressed.

Jobs that use compression

This visibility enables you to effectively manage zEDC (along with many other existing and emerging z/OS technologies) to maximize the benefit that can be achieved from this new technology.

IntelliMagic Vision systems module

This short video provides a demonstration of this type of visibility:



Visit to learn how to manage zEDC more effectively, or request a personalized demo to see the software in your environment.

5 thoughts on “Getting the Most out of zEDC Hardware Compression”

  1. Al says:

    I’ve heard rumors of internal memory constraint issues of the zEDC cards causing batch processing to abend when memory is exhausted. This demo showed zEDC processor utilization, any information on storage usage?

    1. Our customers have indicated satisfaction with zEDC and have not reported these concerns. There is a zEDC abend issue addressed by IBM APAR OA50841: Users of the zEDC services can encounter an ABEND0C4 RSN11 for instances where virtual storage gets paged out due to the module table not being in fixed storage.

      IntelliMagic Vision reports on virtual storage usage for the primary storage areas (private above/below the line, LSQA/SWA, etc.) at the address space level.

      SMF storage usage for zEDC compression for an SMF logstream is reported in SMF 23 records. IntelliMagic Vision does not currently support SMF 23 records.

  2. Jack Hyde says:

    There is a rumor, I don’t know where it came from, that says you can save a load of money by turning off the compression in the middleware and just use the zEDC function in the PCIe card to compress to DASD. Todd-what is the cost benefit you have seen? Does IMVision provide the zEDC cost benefit perspective?

    1. It is true there will be CPU savings from turning off software-based compression and utilizing zEDC hardware compression instead. But zEDC does not currently support all access methods (e.g., DB2 tables), so that is not always an option.

      I am not aware if any of the software-based compression methods externalize their CPU consumption into RMF or SMF records. If they do, IntelliMagic Vision could report on any reduction in CPU consumption. Then you would have to apply your own CPU cost factors.

      Thanks for the good questions.

Leave a Reply