P-Tracker tracks program calls by using, among other things, the SAF interface. There it monitors all activities in the class PROGRAM. It receives the TIOT offset of the calling program - the TIOT contains all DD names of the job - which enables positive identification of the member and program. P-Tracker can be modified as required by the user, for instance to control only calls referencing certain libraries.
Under CICS you normally only see that CICS has loaded a program. That point in time may be far removed from the actual time when the program is used. P-Trackerï¿½s CICS interface makes the real sequence of events visible.
The P-Tracker started task collects all its information in a dataspace and writes it asynchronously into P-Tracker's ï¿½Call Repository.ï¿½ A batch job removes internal administrative data, converts fields to readable format, and copies the user data into a sequential file. This file may be evaluated in place or loaded into a DB2 table for further analysis using SQL queries.
The strengths of P-Tracker:
License administration (Software Asset Management) requires exact information on the usage of certain software products. P-Tracker can tell you, which program was used, how often and by whom. For mainframe z/OS usage, P-Tracker is the most trustworthy source of this information.
tool for inventory, asset management, data center mergers, and program
Systems Associates, Inc.
All trademarks including IBM, DB2, z/OS, IMS, VSAM are of IBM or their respective trademark holders.