You can configure different aspects of utilization tracking
by editing the entries in the utilization tracking configuration file.
The entries are divided into two categories.
- The entries in the Product information category identify
the compiler. Do not modify these entries.
- The entries in the Tracking configuration category can
be used to configure utilization tracking for this product. Changes
to these entries take effect in the usage file upon the next compiler
invocation. In this case, the compiler emits a message to indicate
that the new configuration values have been saved in the usage file.
When you generate a report from the usage file, the new values are
used.
The following rules apply when you modify the entries:
- The following entries are written to the usage files whenever
you change them, and they are used the next time the utilization reporting
tool generates a report from the usage files. These configuration
entries must be the same for all compiler users.
- -qmaxconcurrentusers
- -qexemptconcurrentusers
- -qqualhostname
- If -qqualhostname is changed, you must discard any existing
usage files and start tracking utilization again with new usage files.
Otherwise some invocations are recorded with qualified host names
and some are recorded with unqualified host names.
Notes: - The entries are not compiler options. They can only be used in
the utilization tracking configuration file.
- If the -qexemptconcurrentusers entry is specified multiple
times in the utilization tracking configuration file, all the specified
instances are used. If other entries are specified multiple times,
the value of the last one overrides previous ones.
- The compiler generates a message if you specify the above entries
with different values for different users when using more than one
utilization tracking configuration file. You must modify the entries
to keep them consistent, or make sure all compiler users use a single
utilization configuration file.
Product information
- -qprodId=product_identifier_string
- Indicates the unique product identifier string.
- -qprodVer=product_version
- Indicates the product version.
- -qprodRel=product_release
- Indicates the product release.
- -qprodName=product_name
- Indicates the product name.
- -qconcurrentusagescope=prod | ver | rel
- Specifies the level at which concurrent users are counted, and
their numbers are limited. The suboptions are as follows:
- prod indicates the product level.
- ver indicates the version level.
- rel indicates the release level.
Default: -qconcurrentusagescope=prod
Tracking configuration
- -qmaxconcurrentusers=number
Specifies the maximum number of concurrent users. It is the
number of Concurrent User license that you have purchased for the
product. When the utilization reporting tool generates a report from
the usage file, it determines whether your compiler usage in your
organization has exceeded this maximum number of concurrent users.
Note: You
must update this entry to reflect the actual number of Concurrent
User licenses that you have purchased.
Default: 0
- -qexemptconcurrentusers ="user_account_info_1 [|
user_account_info_2 | ... | user_account_info_n]"
Specify exempt users who have their own Authorized User license.
Exempt users can have as many concurrent invocations of the compiler
as they want, without affecting the number of Concurrent User licenses
available in your organization. When the utilization reporting tool
generates a usage report, it does not include such users in the count
of concurrent users.
user_account_info can
be any combination of the following items:
- name(user_name)
- uid(user_ID)
- host(host_name)
Users whose information matches the specified criteria are considered
exempt users. For example, to indicate that
user1@host1 and
user2@host1 are
exempt users, you can specify this entry in either of the following
forms:
For
user_name,
user_ID,
and
host_name, you can also use a list of user
names, user IDs, or hostnames separated by a space within the parentheses.
For example:
-qexemptconcurrentusers="name(user1 user2)host(host1)"
This
is equivalent to the previous examples.
Note: Specifying this
entry does not exempt users from compiler utilization tracking. It
only exempts them from being counted as concurrent users. To optimize
utilization tracking performance, the format of the specified value
is not validated until the report is produced. For more information
about counting concurrent users, see
Concurrent user considerations.
- -qqualhostname | -qnoqualhostname
Specifies whether host names that are captured in usage files
and then listed in compiler usage reports are qualified with domain
names.
If all compiler usage within your organization is on
machines within a single domain, you can reduce the size of the usage
files by using -qnoqualhostname to suppress domain name qualification.
Default: -qqualhostname,
which means the host names are qualified with domain names.
- -qenabletracking | -qnoenabletracking
Enables or disables utilization tracking.
Default: -qnoenabletracking,
which means utilization tracking is disabled.
- -qusagefileloc=directory_or_ file_name
Specifies the location of the usage file.
By default,
a .cuf file is automatically created for each
user in their home directory. You can set up a central location where
the files for each user can be created. For more information, see Usage file location.
The following rules apply when
you specify this entry:
- If a file name is specified, it must have the .cuf extension.
If the file is a symlink, it must point to a file with the.cuf extension.
If the specified file does not exist, a .cuf file
is created, along with any parent directories that do not already
exist.
- If a directory is specified, there must be exactly one file with
the .cuf extension in the directory. A new file
is not created in this case.
- The path of the specified directory can be a relative or an absolute
path. Relative paths
are relative to the compiler user's current working directory.
Note: If a compiler user cannot access the file, for example,
because of insufficient permissions to use or create the file, the
compiler generates a message and the compilation continues.
You
can use the following variables for this option:
- $HOME for the user's home directory. This allows
each user to have a .cuf file in their home directory
or a subdirectory of their home directory.
- $USER or $LOGNAME for the
user's login user name. You can use this variable to create a .cuf file
for each user and include the user's login name in the name of the .cuf file
or in the name of a parent directory.
- $HOSTNAME for the name of the host on which
the compiler runs. This can be useful when you track utilization across
different hosts.
- -qfileaccessmaxwait=number_of_milliseconds
Specifies the maximum number of milliseconds to wait for accessing
the usage file.
Note: This entry is used to account for unusual
circumstances where the system is under extreme heavy load and there
is a delay in accessing the usage file.
Default: 3000
milliseconds
Notes: - These entries are not compiler options. They can only be used
in the utilization tracking configuration file.
- If the -qexemptconcurrentusers entry is specified multiple
times in the utilization tracking configuration file, all the specified
instances are used. If other entries are specified multiple times,
the value of the last one overrides previous ones.