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.
