This scenario describes an environment where the compilations
are done on multiple machines but all users share a single .cuf file.
The advantage of the approach in this scenario is that using one .cuf file
can simplify the report generation and the usage file pruning process.
The section The number of usage files provides detailed
information about using a single usage file for all compiler users. The .cuf file is already on the machine where
the utilization reporting tool is installed. You do not need to copy
the file to that machine or install the tool on multiple machines
to prune the .cuf files.
This approach has the following disadvantages:
- The compiler users must compete for access to one usage file.
Because the file might become large, it might have an impact on performance.
- Some setup work is required to create the shared .cuf file
and to give all compiler users write access on a network file system.
- The efficiency of the whole process depends on the speed and reliability
of the network file system, because the compilers and the .cuf file
are on different machines. For example, some file systems are better
than others in supporting file locking, which is required for concurrent
access by multiple users.
In this scenario, two compiler users run the compilers on separate
machines and they use one shared .cuf file on
a network file system, such as NFS, DFS, or AFS. 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 multiple machines, with a shared .cuf file - On Machine A and Machine B, mount point /xyz is
created to Machine C. All compiler utilization is recorded in the .cuf file,
from which the usage report is generated.
This diagram reflects the following points:
- Utilization tracking is configured respectively on Machine A and
Machine B.
Notes: - Although each machine has its own configuration file, the contents
of these files must be the same.
- Centrally managing the utilization tracking functionality can
reduce your configuration effort and eliminate possible errors. The Central configuration section provides detailed information
about how you can use a common configuration file shared by compiler
users using different machines.
- A network file system is set up for the central management of
the .cuf files. When user1 and user2 invoke the
compilers from Machine A and Machine B, the utilization information
of both compilers is written to the .cuf file
on Machine C.
- user3 invokes urt to generate usage reports
from the .cuf file on Machine C.
Note: You can use the utilization reporting tool to prune the usage
files regularly to prevent them from growing too big.