HCL Z Asset Optimizer (ZAO) as a Usage Monitor

​At this inflection point of the “Mainframe Evolution”, the current trending term is lowering TCO for mainframes while maintaining the secure, high-performance, and high availability architecture, with the existing suite of mainframe software.

Most CxO are challenged on a “Trusted Chargeback” mechanism with mainframe software vendors. Key considerations are:
 

• With legacy infrastructure and assets built over the years in multiple geographic locations by multiple vendors at various times, mainframe environments today have grown to a complex stature.
• Usage estimates are often grossly underestimated.
• Universally accepted vendor solutions like HCL ZAO for usage monitor.

 
It is imperative to understand the current priorities for the line of business. You’ll need to be aware of your mainframe software usage to make appropriate decisions.
Information around mainframe software usage is a MUST for any migration engagement. Without this information, your business cannot progress towards modernization, chargeback, or licence verification for your assets.
 
This is where the HCL Z Asset Optimizer (HCL ZAO) comes into the picture, specifically designed for IBM Z Systems/Mainframe customers to manage software asset inventory, their usage and license information in one integrated solution.
 
It has browser-based, easy to access real-time usage reports across sysplex environments. If a product can be identified via load modules by name, then you’ll be able to see the usage count (which is an aggregated count). If the same module has been executed from the same library multiple times, the count will show how many times the module was loaded and unloaded successfully, hence the usage.

Browser- based Log-in Screen to analyze the generated reports, requiring to enter a valid username in the Username field. and Enter a valid password in the Password field.

​All Scanned Discovery Data by the Inquisitor batch job that discovers loadable programs in z/OS®data sets and z/OS® UNIX™System Services file systems.
A program locates load libraries on z/OS® DASD devices and captures information about the load modules.

The Assets tab contains query high-level aggregated data, such as product versions. This level of data is useful if you are reconciling product licenses and product usage trends.

​Actual Usage data by Product, Colour code as per the change from previous months.

Product usage across machines with respective value units

​In summary, The Usage Monitor is a server address space, which that runs as a started task. Work is queued to the Usage Monitor from all address spaces where programs are used. To reduce unwanted data, exclusion masking is done based on program name, and/or exclusion masking based on data set name.
The Usage Monitor will attempt to record the CPU time used by each program.
 
In addition, the Usage Monitor performs some basic data aggregation with counters being maintained, so that multiple similar events can be represented by a single record with an associated event count. For those occasions where you want to track individual program management events and ascertain their precise chronology, the Usage Monitor Trace Facility can be employed.
 
Usage Monitor collects usage of CICS regions with the required customization.
 
Finally, for all Mmainframe Uusage monitoring & Rreporting, ZAO is the first pit stop which also comes with flexible pricing options tailored to your needs. 
 
You can schedule a demo to explore more about ZAO’s offering and usage to reduce TCO and have a firm baseline inventory for all vendor interactions.

---

Suresh Narayanan
Mainframe Technical Advisor at HCL Software
 
 Suresh Narayanan is the Mainframe Technical Advisor at HCL Software. Focussing on improving Mmainframe Ssystems & related processes for users to maximize the ROI, thereforehence reducing the TCO. Lead modernization solutions for mainframe environments by performing gap analysis and migration approaches with Aautomation and DevOps practices for Mmainframe customers.