This scenario describes an environment where the compilations
are done on multiple machines and all users have their own usage files.
In this scenario, two compiler users run the compilers on separate
machines and they have their own
.cuf files.
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.
This tool can be run on either of the machines on which the compiler
is installed or on a different machine.
Note: The utilization reporting
tool requires access to all the .cuf files.
You
can use either of the following methods to make the files accessible
in this example:
- Use a network file system, such as NFS, DFS, or AFS.
- Copy the files from their original locations to the machine where
you plan to run the utilization reporting tool. You can use ftp, rcp, rsync or
any other remote copy command to copy the files.
The following diagram illustrates this scenario.
Figure 1. Compiler
users use multiple machines, with multiple .cuf files- user3 copies the .cuf files to Machine C.
A cron job can be created to copy the files automatically on a regular
basis.
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.
- When user1 and user2 invoke the compilers, the utilization information
is recorded in the two .cuf files under their
respective home directories, /home/user1 and /home/user2.
Note: These
.cuf files
can also be created in another common location, for example,
/var/tmp.
The
Usage file location section provides detailed
information about how to create these files in a common location.
- user3 copies the two .cuf files from Machine
A and Machine B to Machine C.
- user3 invokes urt to generate usage reports
from the .cuf files on Machine C.