You can use one usage file or separate usage files for
different compiler users.
Using separate usage files for different compiler
users
The advantages of using separate usage files are as
follows:
- It might provide better performance because compiler users access
their own usage files instead of competing for access to a shared
one and separate usage files are usually smaller.
- Usage file for a user can be automatically created when the user
uses the compiler to compile a program. There is no need to explicitly
create a usage file for each user beforehand. For more information,
see Usage file location.
- When generating utilization reports, you usually include all compiler
users. However, if there are circumstances in which you want to exclude
some users, you can simply omit their usage files when you invoke
the utilization reporting tool. For example, you might want to omit
users who have their own Authorized User license.
The disadvantage is that you might have to maintain separate
usage files for different users.
Using a single usage file for all compiler users
The
advantage of using a shared usage file for all users is that you only
need to maintain a single file instead of multiple files. However,
with a single usage file, you lose the flexibility and possible performance
benefits of using multiple usage files, as described in the preceding
subsection.
The compiler provides an empty usage file urtstub.cuf in
the usr/vac/urt directory. You can
create a usage file for all compiler users by copying the empty usage
file to a directory where they all have write access. In this case,
you need to change the -qusagefileloc entry
in the utilization tracking configuration file to point to the location
of the usage file.