zPulse · CPU · Formerly EAMC
zPulse CPU builds the MSU profile of each LPAR from your RMF or CMF reports, with the four-hour rolling average (R4HA), WLM workloads and the coupling facility. It replaces EAMC, with history and a daily mail.
MSU consumption drives software cost, so the questions are practical: which LPAR, at what hour, and how close to the defined capacity. zPulse CPU answers them for one partition or for all the partitions of a sysplex.
zPulse CPU is the module for processor consumption. It reads the CPU, partition, workload and coupling facility pages of your RMF or CMF reports and keeps the MSU history from one run to the next.
What it analyses
MSU used and defined for all LPARs together, with the LPAR weights, and the same view for a single LPAR.
The four-hour rolling average of MSU by LPAR, with the capacity and the capping.
Interrupt rate, MVS busy, LPAR busy, CPU used and weight, from the CPU and partition data of your reports.
CPU, service units and I/O rate by workload; I/O rate and QI by service class and report class; the worst periods. QI is the I/O rate times the disconnect, pending and IOSQ time.
CMPR busy and SCM busy by I/O processor, and, from RMF reports only, the activity of each coupling facility.
Power use linked to the CPU, from the RMF power consumption report only.
In the application
These are the report tabs of a study in the zPulse application.
The CPU report tabs of a study in the zPulse application.
The workload manager tabs.
Data
zPulse works from the reports and files you already produce. Nothing is installed on z/OS.
| Record or file | Report | What zPulse uses it for |
|---|---|---|
| SMF 70.1 | CPU Activity, Partition Data (RMF); CPU Utilization (CMF) | MSU by LPAR, R4HA, LPAR activity. |
| SMF 78.3 | I/O Queuing Activity | CMPR busy and SCM busy by I/O processor. |
| SMF 72.3 | Workload Activity | CPU, service units and I/O rate by workload, service class and report class. |
| SMF 74.4 | Coupling Facility Activity (RMF) | Sysplex coupling facility activity. RMF reports only: the screen is empty for CMF files. |
| SMF 70.1 | Power Consumption (RMF) | Electricity consumption of the CPU. RMF reports only, with z/OS 3.1 or later and POWERMETRICS; CMF files carry no power data. |
SMF 70.1
SMF 78.3
SMF 72.3
SMF 74.4
SMF 70.1
Tools
Tools open a report or a folder and show charts and tables on one subject. Each card of the catalogue says which file the tool reads.
Automatic studies
A scheduled CPU study sends one mail per configuration and per time period, each with three charts per LPAR: average MSU, sum of MSU and maximum R4HA. The same charts cover the previous days. The period covered is in the subject.
EAMC created an MSU and MIPS profile for your LPARs. zPulse CPU keeps the MSU profile and adds the R4HA, WLM and coupling facility views. MIPS views are not produced by zPulse today: the TS AddInfo EAMC tool shows them only from MIPS files written by the former EAMC.
MSU by hour, stacked by LPAR, with the Max R4HA
Previous days: Max R4HA (MSU)
The mail charts up to 60 previous days.
Period: 7 Oct 2026 · Charts are in the body of the mail, with no attachment.
FAQ
RMF post-processor reports and CMF reports, as text files, for one LPAR or for all the LPARs of a sysplex. The CPU and partition data come from SMF 70.1, the workload data from SMF 72.3 and the coupling facility data from SMF 74.4.
As a four-hour rolling average of the MSU used by each LPAR, shown with the capacity and the capping.
Yes. CPU activity can be shown for all the LPARs together or for a single LPAR. The CPU MSU mail is sent per configuration.
Not by itself. zPulse writes MSU files only. The MIPS views of the TS AddInfo EAMC tool need MIPS files produced by the former EAMC.
No. zPulse reads the report files you already produce. It runs on its own server.
zPulse
Formerly EADM
Response time by component, hot volumes, cache, FICON channels, I/O topology.
Formerly EATM
Tape catalogue capacity, virtual tape mounts and response time, TS7700 VEHSTATS statistics.
DCOLLECT studies
Allocated and free space, fragmentation and defrag score by LPAR, storage group and volume.
Send us an extract. A Technical Storage expert runs it through zPulse and walks you through the results.