P-Tracker Modernization Guide

P-Tracker monitors program and load module usage on z/OS systems. It tracks who accessed which modules, when they were accessed, and the relationships between modules.

P-Tracker is a software tool designed to provide insights into application and software product usage on mainframe systems.

Organizations that rely on the z/OS operating system, particularly those in industries like banking, finance, and insurance, find P-Tracker valuable for monitoring software usage and ensuring compliance.

A company should consider using P-Tracker when it needs to understand how its software assets are being used, identify potential cost savings, or ensure compliance with licensing agreements.

Alternatives to P-Tracker include IBM Z Software Asset Management. P-Tracker distinguishes itself by focusing on detailed load module usage and inter-module dependencies.

P-Tracker runs on the z/OS operating system and requires access to system libraries and load modules. It can monitor applications running in environments like IMS and CICS.

Yes, P-Tracker runs within an LPAR on a z/OS system. It leverages z/OS system services to gather information about load module usage.

P-Tracker discovers load modules by scanning specified libraries on the z/OS system. It identifies modules and their attributes, such as size, creation date, and associated programs.

P-Tracker reports on modules calling other modules by analyzing load module dependencies. It identifies which modules are invoked by other modules, providing a call graph of application components.

P-Tracker helps organizations optimize software licensing costs by providing detailed usage information. This allows them to identify underutilized software and reallocate licenses as needed.

By monitoring application usage, P-Tracker helps organizations understand how their applications are being used and identify areas for improvement. This can lead to better performance and user satisfaction.

P-Tracker can help organizations ensure compliance with software licensing agreements by providing accurate usage data. This reduces the risk of non-compliance penalties.

P-Tracker controls access to mainframe datasets by integrating with z/OS security systems such as RACF, ACF2, or Top Secret. It leverages these systems to determine who is authorized to access specific load modules.

P-Tracker provides audit logging capabilities that track who accessed which load modules and when. This information can be used to investigate security incidents and ensure accountability.

P-Tracker supports various authentication methods, including those provided by z/OS security systems like RACF, ACF2, and Top Secret. It integrates with these systems to authenticate users.

P-Tracker is typically deployed on-premise within the z/OS environment. It requires access to system libraries and load modules to collect usage data.

Implementing P-Tracker requires a moderate level of technical expertise, particularly in z/OS systems administration and security. Familiarity with RACF, ACF2, or Top Secret is beneficial.

Ongoing operational requirements include monitoring P-Tracker's performance, ensuring it has access to the necessary system resources, and reviewing audit logs for security incidents.

Common implementation challenges include configuring P-Tracker to access the correct system libraries, integrating it with existing security systems, and ensuring it does not impact system performance.