Setting up and checking your AIX environment

Set up the right environment for the AIX® JVM to run correctly during AIX installation from either the installp image or the product with which it is packaged.

Note that the 64-bit JVM can work on a 32-bit kernel if the hardware is 64-bit. In that case, you must enable a 64-bit application environment using smitty:System Environments -> Enable 64-bit Application Environment.

Occasionally the configuration process does not work correctly, or the environment might be altered, affecting the operation of the JVM. In these conditions, you can make checks to ensure that the JVM's required settings are in place:

  1. Check that the SDK and JRE files have been installed in the correct location and that the correct permissions are set. See the User Guide for more information about expected files and their location. Test the java and javac commands to ensure they are executable.

    The default installation directory is in /usr/java6 for the 32-bit JVM and /usr/java6_64for the 64-bit JVM. For developer kits packaged with other products, the installation directory might be different; consult your product documentation.

  2. Ensure that the PATH environment variable points to the correct Java™ executable (using which java), or that the application you are using is pointing to the correct Java directory. You must include the correct Java directory in your PATH environment variable . If it is not present, add it by using the appropriate export PATH=</directory>:$PATH statement; see Setting the path.
  3. Ensure that the LANG environment variable is set to a supported locale. You can find the language environment in use using echo $LANG, which should report one of the supported locales as documented in the User Guide shipped with the SDK.
  4. Ensure that all the prerequisite AIX maintenance and APARs have been installed. The prerequisite APARs and filesets will have been checked during an install using smitty or installp. You can find the list of prerequisites in the User Guide that is shipped with the SDK. Use lslpp -l to find the list of current filesets. Use instfix -i -k <apar number> to test for the presence of an APAR and instfix -i | grep _ML to find the installed maintenance level.

The ReportEnv tool, available from the Java service team, plugs into your JVM and reports on the JVM environment in real time. Your JVM environment affects the operation of the JVM. ReportEnv reports on environment variables and command-line parameters. It is a GUI tool, although it can be run without a GUI. The GUI allows you to browse your environment and, to some extent, dynamically change it. The tool also has a mechanism to generate reports to tell you the exact state of your JVM environment. The ReportEnv tool is available on request from jvmcookbook@uk.ibm.com.

Directory requirements

The system dump agent must be configured to target a directory.

Both the user running the Java application and the group the user is in must have execute and write permissions for that directory. This can be set using the IBM_COREDIR environment variable.

The system dump agents can also be configured on the command line. See Using dump agents for more information.



© Copyright IBM Corporation 2005, 2010. All Rights Reserved.
© Copyright Sun Microsystems, Inc. 1997, 2007, 901 San Antonio Rd., Palo Alto, CA 94303 USA. All rights reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This information center is powered by Eclipse technology. (http://www.eclipse.org/)