If your system uses the en_US locale and encoding, the compiler message catalogs are automatically configured to display correctly, regardless of whether you used the basic or advanced method of installation and configuration. However, if your system uses any other supported locale (for a list of supported language locales, see National language support), you must set the NLSPATH environment variable, so that the compiler and runtime functions can find the appropriate message catalogs after the installation. However, if your system uses the en_US.utf8 encoding, you must set the NLSPATH environment variable, so that the compiler and runtime functions can find the appropriate message catalogs after the installation.
export NLSPATH=$NLSPATH:
xlsmprt_path/msg/%L/%N:
xlrte_path/msg/%L/%N:
xlcmp_path/vacpp/bg/12.1/msg/%L/%N
setenv NLSPATH $NLSPATH:
xlsmprt_path/msg/%L/%N:
xlrte_path/msg/%L/%N:
xlcmp_path/vacpp/bg/12.1/msg/%L/%N
Accessing the compiler message catalogs from an I/O node
Before an I/O node can access the compiler message catalogs, it needs to know their location on the Front-end node. This section describes how to set up the I/O node so it can access these messages in a default or non-default location on a Front-end node.
Default message location
The default location for the compiler message catalogs is /opt/ibmcmp/. To indicate this location to an I/O node, export /opt/ibmcmp/ from the Front-end node and mount this path to the I/O node.
/opt/ibmcmp/ machine1
/usr/sbin/exportifs -ra
mount frontend1:/opt/ibmcmp/ /opt/ibmcmp/