What infrastructure is required?

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.

For mainframe products: Does this run in an LPAR?

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.

How does P-Tracker provide business value?

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.

How does P-Tracker improve application performance?

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.

How does P-Tracker help with compliance?

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

How does P-Tracker provide security?

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.

What audit logging capabilities exist?

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.

What authentication methods are supported?

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.

How is P-Tracker typically deployed?

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.

What level of technical expertise is required to implement it?

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.

What ongoing operational requirements exist?

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.

What are common implementation challenges?

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.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

P-Tracker

Name: P-Tracker
Availability: InStock

UBS Hainer Active z/OS

Program and Load Libraries Infrastructure and Computing Assets Data Discovery Mining and Processi

Vendor

UBS Hainer

Product Overview

P-Tracker is a software tool designed to monitor program and load module usage on z/OS systems. From an architectural perspective, P-Tracker operates as a standalone application within the z/OS environment, leveraging system services to gather information about load module usage. It integrates with z/OS security systems such as RACF, ACF2, and Top Secret to control access to usage data and ensure security.

The main system components include data collection modules, a reporting engine, and a user interface. These components communicate through internal APIs and data structures. P-Tracker stores usage data in VSAM datasets or DB2 tables, depending on the configuration.

The architecture supports both batch and online reporting, allowing users to access usage data in real-time or generate historical reports. 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.

The tool 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's architecture is designed for scalability and performance, ensuring that it can handle large volumes of usage data without impacting system performance.

Frequently Asked Questions

What does P-Tracker do?

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.

Is this a system, application, or tool?

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

What types of organizations use this?

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.

When should we consider P-Tracker?

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.

What are the alternatives to P-Tracker?

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.

Related Products

ASG-Vista was designed to graphically represent IT assets and their relationships, offering a visual understanding of the IT infrastructure. It supported platforms such as z/OS,...

Infrastructure and Computing Assets Data Discovery

View Details →

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Are You a Vendor? Claim Your Listing

P-Tracker

Product Overview

Frequently Asked Questions

What does P-Tracker do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider P-Tracker?

What are the alternatives to P-Tracker?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

How does P-Tracker discover load modules?

How does P-Tracker report on module dependencies?

How does P-Tracker provide business value?

How does P-Tracker improve application performance?

How does P-Tracker help with compliance?

How does P-Tracker provide security?

What audit logging capabilities exist?

What authentication methods are supported?

How is P-Tracker typically deployed?

What level of technical expertise is required to implement it?

What ongoing operational requirements exist?

What are common implementation challenges?

Related Products

More from UBS Hainer

BCV4

BCV5

BCV6

BPA4DB2

BTO

SQLQC

Similar Products

Adabas Text Retrieval

Application Discovery

Application Discovery and Delivery Intelligence

ASG-becubic

ASG-Manager Products

ASG-Vista

Help Improve This Directory

Share Your Product Experience