Scenario: One machine, one shared .cuf file

This scenario describes an environment where all the compilations are done on one machine and all users share one .cuf file.

The advantage of using the approach in this scenario is that it simplifies report generation and usage file pruning, because the utilization report tool only need to access one .cuf file. The disadvantage is that all compiler users need to compete for access to this file. Because the file might become large, it might have an impact on performance. Some setup work is also required to create the shared .cuf file and to give all compiler users write access. The The number of usage files section provides detailed information about using a single usage file for all compiler users.

In this scenario, two compiler users run the compiler on the same machine and their utilization information is recorded in a shared .cuf file. The utilization tracking configuration file for the compiler is modified to point to the location of the .cuf file. When the compiler is invoked, it writes the utilization information to that file. You can then use the utilization reporting tool to retrieve the utilization information from the file and generate usage reports.

The following diagram illustrates this scenario.
Figure 1. Compiler users use a single machine, with a shared .cuf file
urt scenario 2
  1. Both user1 and user2 need write access to the .cuf file in /xyz.
  2. user3 needs read access to the .cuf file in/xyz to generate the usage report, and write access to prune the .cuf file.
  3. A cron job can be created to run urt automatically on a regular basis.
The diagram reflects the following points:
  1. user1 and user2 use the same utilization tracking configuration file, which manages the tracking functionality centrally. A common location /xyz is created to keep a shared .cuf file.
  2. When user1 and user2 invoke the compiler, the utilization information is recorded in the .cuf file under the common directory /xyz.
  3. user3 invokes urt with -qusagefileloc=/xyz to generate usage reports.
Note: Regular running of the utilization reporting tool can prevent these files from growing too big, because you can prune the usage files with this tool.

Related information