There are optional setup and verification procedures that
you can use after you have installed the compiler. You might also
want to use the product documentation.
Checking compiler and fileset information
You can check the versions of the compiler and individual
filesets installed by using the lslpp command,
the -qversion compiler option, or by viewing the .vrmf_history file.
Enabling utilization tracking
Utilization tracking can be used to detect whether the
compiler usage exceeds your entitlement based on the number of Concurrent
User licenses you have purchased.
Enabling IBM License Metric Tool (ILMT) and Tivoli Asset Discovery for Distributed (TADd)
IBM® License Metric
Tool (ILMT) and Tivoli® Asset
Discovery for Distributed (TADd) can help you manage software usage
metering and license allocation services on supported systems. In
general, ILMT and TADd recognize and monitor the products that are
installed and in use on your system.
Setting environment variables
Before using the compiler, verify that the environment
variables LANG, MANPATH, NLSPATH, and PATH are set.
Enabling the XL C error messages
If your system uses the en_US locale and encoding, the
compiler message catalogs are automatically configured to display
correctly, whether you used the basic or advanced method of installation
and configuration. However, if your system uses any other supported
locale, you must set the NLSPATH environment variable so that the
compiler and runtime functions can find the appropriate message catalogs
following installation.
Enabling the manual pages
Manual pages are provided for the compiler invocation commands
and other compiler utilities.
Creating shortcuts to the XL C invocation commands The compiler invocation
commands are not automatically installed in /usr/bin/.
To invoke the compiler without having to specify the full path, create
a shortcut to the invocation commands.
Accessing the local documentation
Help using IBM XL
C for AIX®, V13.1 is
available in both HTML and PDF formats. Manual pages for the compiler invocation
commands and other command utilities are also included.
Testing the installation
To test the product installation and the critical
search paths, try building, compiling, and running a simple program.