Scenario: One machine, multiple .cuf files

This scenario describes an environment where all the compilations are done on one machine and all users have their own .cuf files.

The approach in this scenario has the following advantages: However, using multiple .cuf files that are automatically created in each user's home directory might have the following issues: Instead of using each user's home directory, the .cuf files for each user can be created in a common location. The Usage file location section provides detailed information about how to create these files in a common location.

In this scenario, two compiler users run the compiler on the same machine and they have their own .cuf files. When the compiler is invoked, it automatically creates a .cuf file for each user and 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 one machine, with separate .cuf files
urt scenario 1
  1. user3 needs read access to .cuf files in /home/user1 and /home/user2 to generate the usage report, and write access to prune the usage files.
  2. A cron job can be created to run urt automatically on a regular basis.
This diagram reflects the following points:
  1. user1 and user2 use the same utilization tracking configuration file, which manages the tracking functionality centrally.
  2. When user1 and user2 invoke the compiler, the utilization information is recorded in the two .cuf files under their respective home directories, /home/user1 and /home/user2.
  3. user3 invokes urt with -qusagefileloc=/home/user1:/home/user2 to generate usage reports.
    Note: If you need to find out which home directories contain usage files, you can invoke urt as follows:
    urt -qusagefileloc=/home -qmaxsubdirs=1
    In this case, urt looks for .cuf files in all users' home directories.

Related information