P-Tracker supports efficient Software Asset Management. It is a high performance tracking tool, a comprehensive software catalog, and a straightforward reporting tool. P-Tracker has powerful functions but a small footprint, and it helps to keep Software Asset Management simple, efficient, and cost effective.
As a high performance tracking tool, P-Tracker recognizes any program execution in z/OS systems. It records the program name and the name of the load library from where a program has been loaded. Furthermore it delivers information about: who, or, what, demanded the execution (user, job, task), where it has been executed (system, LPAR), and when it has been executed (date, time).
As a comprehensive software catalog, P-Tracker accommodates all and any pieces of software that move (and sleep) in z/OS systems. It identifies product names, vendor names, release numbers, module names, libraries with their location, duplicates of modules and libraries. It stores and regularly updates those pieces of information and the resulting catalog can be searched and modified ad libitum.
As a straightforward reporting tool, P-Tracker combines the recorded program executions with the software catalog and reveals accurate figures about the real life of your software assets. Various reports demonstrate software usage, usage periods, intervals, and frequency, and they also show what has not been used for a long time. CSV output goes directly into your spread sheets and easily generates graphical images for your reports.more»
P-Tracker is the ultimate tool for clearly answering the usual questions of Software Asset Management, for example:
- What applications/products are installed on our systems?
- Who is using them? How often? When?
- Is the usage ratio increasing or decreasing (trend graphs to support renewal/upgrade negotiations)?
- Are there products/applications that are never being used?
- Which products are seldom/frequently used?
- Is the current license fee justified given the low utilization?
- Are different users using different versions of the same software product? Or compatible products?
- How can we consolidate redundant, or similar products (inherited from company mergers)? Which products should remain?
- How do load libraries, products, features, components and versions interrelate?
- Who would be impacted by an upgrade?
- Who would be impacted by a replacement (training)?
- Which products/libs/modules is a job using (error analysis)?
- What maintenance levels are deployed?
- What needs to be replicated in our Disaster Recovery Systems?
P-Tracker helps with many SAM related issues
Let‘s take the simple case of LPAR licenses where the LPAR size needs to increase due to higher demands of the core application. Concurrently, the product usage of another vendor‘s products running on the same LPAR will remain the same, but the license fees are due to increase.
P-Tracker‘s usage stats will empower you, the user, during discussions with the vendor, because now you know precisely how much a product is actually being used. And, in situations where a replacement is the only option on the table, you know in advance which in-house users are affected, and, who needs to be retrained in using the new product.
With in-house software, it is estimated that production libraries increase by 5% of defunct software modules each year due to the fact that they must allow for back-out processes (don‘t delete, rename). That means that after five years, approximately 28% of the modules in a library are no longer being used, and yet, they are still contracted for maintenance by in-house or outsourced staff. P-Tracker identifies unused modules.
Change is inevitable, hardware is upgraded, or removed, but, sometimes the license fees of depending and obsolete software are still paid on time! P-Tracker‘s inventory/usage reports can protect you from unnecessary payments.
You likely will also use P-Tracker to:
- Consolidate product machine/system coverage and to optimize sub-capacity licenses
- Prove to management that your budget is fully utilized in order to avoid funding cuts or to justify increases
- Become »audit ready« to avoid costly license compliance violations
- To conduct product inventory verification
- To conduct an audit trail of product use per LPAR