Expertise
Thirty years of z/OS storage expertise, behind the tool
zPulse automates the analysis. Our engineers have spent thirty years reading z/OS storage data. Use the tool on its own, or have an expert read the results with you.
Our offers
From a free study to a recurring review
Start with your own data, at no cost. Go further only when the results justify it.
01Start here
Free study
Send RMF or CMF reports and a DCOLLECT extract. An expert analyses them in zPulse and presents the results to you.
- Free of charge
- Results video call and written report
- Your files deleted after 30 days
02One-off
Audit
A defined question, answered by an expert with zPulse on your data.
- Performance
- Capacity
- DASD and tape tuning
- Disk array migration
03Ongoing
zPulse and expert review
zPulse on your own data, and recurring studies commented by a Technical Storage expert.
- Recurring studies, commented by an expert
- Support included in the licence
- Training included in the licence
Why an expert
A graph tells you something is slow. Experience tells you why.
zPulse reads RMF and CMF reports, DCOLLECT extracts and tape catalogues, and turns them into response-time breakdowns, cache and queuing indicators, capacity trends and tape activity, far faster than by hand.
The tool does the counting. The expert does the reading: which of these ten curves matters on your site, what changed after last month's migration, which setting to touch first and which to leave alone.
That combination is what we sell: the software, and the people who built it and use it on real z/OS estates.
Trust… but verify. Every number in a report should lead you back to the data it came from.
Audit
What a one-off audit covers
Scope is agreed with you beforehand. The usual subjects are these four.
Capacity
DASD and tape tuning
Disk array migration
Included in the licence
Support and training come with zPulse
You do not buy them separately. They are part of the licence.
Support
Training
Use case
An insurance group finds the real source of its slow batch window
- Context
- The nightly batch window was overrunning on some mornings. Monitoring showed nothing unusual on the volumes involved.
- What the study showed
- Pending time on a group of volumes came from contention in one array's back end, caused by a data copy job scheduled at the same hour.
- What changed
- The copy job moved to another window. Response time on those volumes fell by about a third, and the batch window stopped overrunning.
Get a free study of your own data
Send us your reports and extracts. An expert analyses them in zPulse and presents the results to you.