This product is also based in part on the work of the FreeType Project. For more information about FreeType see http://www.freetype.org
The IBM AIX Developer Kit, JavaTM2 Technology Edition, Version 1.2.2 Development Team welcomes feedback on this release. Please visit http://www.ibm.com/java/jdk/support/ for information on reporting bugs and any other related correspondence.
This README file is part of a release and is applicable only to that particular release. Please ensure that you have the README file appropriate to the release you are using. After installation the response to the command
DE_CH | De_CH | de_CH | DE_DE | De_DE |
ES_ES | Es_ES | es_ES | FR_BE | Fr_BE |
fr_BE | FR_CA | Fr_CA | fr_CA | Fr_CH |
fr_CH | FR_CH | FR_FR | Fr_FR | fr_FR |
IT_IT | It_IT | it_IT | JA_JP | Ja_JP |
ja_JP | KO_KR | ko_KR | PT_BR | Pt_BR |
pt_BR | SV_SE | Sv_SE | sv_SE | ZH_CN |
Zh_CN | zh_CN | ZH_TW | Zh_TW | zh_TW |
To disable the JIT compiler, set the JAVA_COMPILER environment variable to "NONE". This can be done in one of the following ways:
For the Korn shell:
Note: If JAVA_COMPILER="" or -Djava.compiler="" then the JIT compiler will be switched off. If JAVA_COMPILER is set but set to nothing, for example:
The 'green threads' implementation is no longer supported.
When executing a JNI program (e.g., an executable that creates and initialises a JVM and then runs .class files on that JVM), you should be sure that the CLASSPATH is set-up correctly to enable the JVM to find your class files. If you modify the JavaTM2 boot class path, then you should be sure to include the IBM AIX Developer Kit, JavaTM2 Technology Edition, Version 1.2.2 files necessary to run your applications.
This product has made use of AIX 4.3.3 extensions to enable faster and more efficient execution without impacting non-Java applications.
The launchers, and other programs in this release, will use these extensions automatically, but their use by another program requires that it is linked with an additional AIX binder option ("-bM:UR"). If you develop a JNI program that creates and attaches to the JVM in this and future releases, then this binder option is required.
A side-effect of this requirement is that such JNI executable programs, including third-party software packages and those built for previous Java software releases on AIX, that were built without this binder option are NOT compatible with the JVM in this release.
Compatibility of an executable program can be verified using
A script file (convertJNI) is shipped in the directory /usr/java_dev2/sdk/sh. This script will help you to convert the modtype to UR in the optional header of your JNI executable programs without having to recompile the code.
The IBM AIX Developer Kit, JavaTM2 Technology Edition, Version 1.2.2 uses an advanced IBM technology called Mixed Mode Interpreter (MMI) which significantly reduces the start up time of the JVM. The MMI and Just In Time (JIT) compiler make use of internal calling conventions and SIGTRAP signals that may make debugging of JNI programs using dbx more difficult.
The IBM AIX Developer Kit, JavaTM2 Technology Edition, Version 1.2.2 handles various AIX signals. Where signal handlers are installed by JNI invocation API applications prior to launching the JVM, the JVM will attempt to chain to the existing handlers when receiving unexpected signals.
Java threads created by the IBM AIX Developer Kit, JavaTM2 Technology Edition, Version 1.2.2 uses the POSIX(R) pthreads model supported on AIX 4.3.3. Currently this is on a 1 to 1 mapping with the kernel threads. When developing a JNI program, it may be advisable to use this mapping if creating pthreads in your own program. This can be controlled using the following environment setting:
To use the JDBC-ODBC Bridge, you need to set up your own ODBC driver to work with the target database. You should only set up the JDBC-ODBC bridge after you have successfully tested your ODBC driver. Check the following website to obtain information about ODBC drivers for your DB2 Universal database or for non IBM databases. The ODBC driver will typically be in libodbc.a in /usr/lib. This library will be imported during the time when the JDBC-ODBC Bridge library libJdbcOdbc.a is loaded at run time.
The Bridge is expecting member libodbc.o in libodbc.a. Check the member name in your libodbc.a using the following command:
To extract and rename the member, then do the following:
If you plan to or already use the BigDecimal class and wish to use the enhanced BigDecimal class then use the import statement:
The new class is automatically available in /usr/java_dev2/jre/lib/rt.jar.
For further details of this support, please see /usr/java_dev2/docs/rmi-iiop/readme.html.
For further details of this extension, please see /usr/java_dev2/docs/JAAS/readme.jaas.ibm, after installing the Java_dev2.ext.jaas fileset.
The Java_dev2.ext.commapi fileset provides serial and parallel port definitions and communications drivers.
For API details see http://www.javasoft.com/products/javacomm/
PTF# | APAR# | Fileset | VRMF |
U467183 | IY03993 | bos.adt.include | 4.3.3.1 |
U467290 | IY06365 | bos.net.tcp.client | 4.3.3.3 |
U467478 | IY04069 | bos.sysmgt.serv_aid | 4.3.3.2 |
U467572 | IY05690 | X11.base.lib | 4.3.3.2 |
U467473 | IY05697 | X11.adt.motif | 4.3.3.1 |
U467558 | IY05741 | X11.base.rte | 4.3.3.2 |
U467459 | IY05989 | X11.Dt.rte | 4.3.3.3 |
U467557 | IY05989 | X11.motif.mwm | 4.3.3.1 |
U467458 | IY05990 | X11.motif.lib | 4.3.3.2 |
U467616 | IY05990 | X11.compat.lib.X11R5 | 4.3.3.2 |
U467283 | IY06171 | bos.rte.libpthreads | 4.3.3.3 |
U467444 | IY06171 | bos.adt.prof | 4.3.3.3 |
U467222 | IY06121 | X11.Dt.lib | 4.3.3.2 |
And ONE of the following two APARs, depending on whether your system is a Uniprocessor (bos.up) or Multiprocessor (bos.mp): | |||
U467275 | IY06625 | bos.up | 4.3.3.3 |
U467531 | IY06625 | bos.mp | 4.3.3.3 |
The above APARs for all locales are not on the AIX 4.3.3 GA installation media, but can be obtained from IBM if they are not already on your AIX system. The easiest way to upgrade is using the FixDist tool, available from (see http://service.software.ibm.com/cgi-bin/support/rs6000.support/downloads).
The Java_dev2.rte package (listed above) requires the following AIX base level filesets for specific locales or for DBCS locales. If they are not already installed, they can be found on the AIX 4.3.3 GA installation media.
PTF# | APAR# | Fileset | VRMF |
U469092 | IY06121 | bos.loc.iso.th_TH | 4.3.3.1 |
U469091 | IY06121 | bos.loc.iso.Vi_VN | 4.3.3.1 |
U467545 | IY05472 | bos.loc.iso.zh_TW | 4.3.3.1 |
The above APARs, for specific or DBCS locales, are not on the AIX 4.3.3 GA installation media, but can be obtained from IBM if they are not already on your AIX system. The easiest way to upgrade is using the FixDist tool, available from (see http://service.software.ibm.com/cgi-bin/support/rs6000.support/downloads).
After you have made the changes to the .hotjava/properties file, then you should be able to run the appletviewer.
On AIX 4.3.3 (and upwards) the Euro is supported via the new UTF8 locales. This is the primary mechanism for Euro support on the AIX operating system. Applications can then make use of the Euro symbol, which looks like a C with an = superimposed on it and can be created using Unicode character '\u20AC'. Euro variants of Java software locales, which provide the appropriate currency formatting, can also be used by Java applications. The environment variable LC_MONETARY is currently not used by this Java implementation, the default is always the national currency.
For more information on IBM's position on the Euro currency, see http://www.ibm.com/euro.
Note: use of this variable is discouraged, and it may be removed at a later date.
In the IBM AIX Developer Kit, JavaTM2 Technology Edition, Version 1.2.2, CPU times are not able to be recorded through the HPROF profiler tool. This restriction also applies to any tools that make use of the JVMPI. As a result, CPU times will be returned as 0 from the JVMPI and displayed as NaN in the HPROF output.
IBM intends to fully support the JVMPI and these temporary restrictions are planned to be lifted in a future release of the IBM AIX Developer Kit, JavaTM2 Technology Edition or earlier.
IBM now fully supports the Java Virtual Machine Debugging Interface (JVMDI).
There are two ways to correct this problem:
Support for the new UTF8 locales has been added, and so has support for IBM-1252 locales, either of which is required to make use of the Euro currency functionality.
There is a known problem with "Yen" and backslash characters having the same value for locale Ja_JP. This problem will be resolved when the codepage support for Cp943c ( Ja_JP.IBM-943) and Cp942c ( Ja_JP.IBM-942) in AIX is fixed.
LOCALE | NAME | ENCODING | TRANSLATIONS |
Albanian | SQ_AL | UTF8 | |
SQ_AL | UTF8 | ||
Arabic | AR_AA | UTF8 | |
AR_AA | UTF8 | ||
Bulgarian | bg_BG | ISO8859-5 | |
BG_BG | UTF8 | ||
Byelorussian | BE_BY | UTF8 | |
Catalan | ca_ES | ISO8859-1 | |
ca_ES | IBM-1252 | ||
CA_ES | UTF8 | ||
Ca_ES | IBM-850 | ||
Chinese (Simplified) | zh_CN | GB2312 | yes |
Zh_CN | GBK | yes | |
ZH_CN | UTF8 | yes | |
Chinese (Traditional) | Zh_TW | Big5 | yes |
zh_TW | CNS11643 | yes | |
ZH_TW | UTF8 | yes | |
Croatian | hr_HR | ISO8859-2 | |
HR_HR | UTF8 | ||
Czech | cs_CZ | ISO8859-2 | |
CS_CZ | UTF8 | ||
Danish | da_DK | ISO8859-1 | |
Da_DK | IBM-850 | ||
DA_DK | UTF8 | ||
Dutch (Belgium) | nl_BE | ISO8859-1 | |
nl_BE | IBM-1252 | ||
Nl_BE | IBM-850 | ||
NL_BE | UTF8 | ||
Dutch | nl_NL | ISO8859-1 | |
nl_NL | IBM-1252 | ||
NL_NL | UTF8 | ||
Nl_NL | IBM-850 | ||
English (Great Britain) | en_GB | ISO8859-1 | yes |
EN_GB | UTF8 | yes | |
En_GB | IBM-850 | yes | |
English (United States) | en_US | ISO8859-1 | yes |
EN_US | UTF8 | yes | |
En_US | IBM-850 | yes | |
Estonian | ET_EE | UTF8 | |
Finnish | fi_FI | ISO8859-1 | |
fi_FI | IBM-1252 | ||
FI_FI | UTF8 | ||
Fi_FI | IBM-850 | ||
French (Belgium) | fr_BE | ISO8859-1 | yes |
fr_BE | IBM-1252 | yes | |
FR_BE | UTF8 | yes | |
Fr_BE | IBM-850 | yes | |
French (Canada) | fr_CA | ISO8859-1 | yes |
FR_CA | UTF8 | yes | |
Fr_CA | IBM-850 | yes | |
French (France) | fr_FR | ISO8859-1 | yes |
fr_FR | IBM-1252 | yes | |
FR_FR | UTF8 | yes | |
Fr_FR | IBM-850 | yes | |
French (Switzerland) | fr_CH | ISO8859-1 | yes |
FR_CH | UTF8 | yes | |
Fr_CH | IBM-850 | yes | |
German | de_DE | ISO8859-1 | yes |
de_DE | IBM-1252 | yes | |
DE_DE | UTF8 | yes | |
De_DE | IBM-850 | yes | |
German (Switzerland) | de_CH | ISO8859-1 | yes |
DE_CH | UTF8 | yes | |
De_CH | IBM-850 | yes | |
Greek | el_GR | ISO8859-7 | |
EL_GR | UTF8 | ||
Hebrew | HE_IL | UTF8 | |
Hungarian | hu_HU | ISO8859-2 | |
HU_HU | UTF8 | ||
Icelandic | is_IS | ISO8859-1 | |
IS_IS | UTF8 | ||
Is_IS | IBM-850 | ||
Italian | it_IT | ISO8859-1 | yes |
it_IT | IBM-1252 | ||
IT_IT | UTF8 | yes | |
It_IT | IBM-850 | yes | |
Japanese | ja_JP | IBM-eucJP | yes |
Ja_JP | IBM-932 | yes | |
Ja_JP | IBM-943 | yes | |
JA_JP | UTF8 | yes | |
Korean | ko_KR | KSC5601 | yes |
KO_KR | UTF8 | ||
Latvian | LV_LV | UTF8 | |
Lithuanian | LT_LT | UTF8 | |
Macedonian | mk_MK | ISO8859-5 | |
MK_MK | UTF8 | ||
Norwegian | no_NO | ISO8859-1 | |
NO_NO | UTF8 | ||
No_NO | IBM-850 | ||
Polish | pl_PL | ISO8859-2 | |
PL_PL | UTF8 | ||
Portuguese (Brazil) | pt_BR | ISO8859-1 | yes |
PT_BR | UTF8 | yes | |
Pt_BR | IBM-850 | yes | |
Portuguese | pt_PT | ISO8859-1 | |
pt_PT | IBM-1252 | ||
PT_PT | UTF8 | ||
Pt_PT | IBM-850 | ||
Romanian | RO_RO | UTF8 | |
Russian | ru_RU | ISO8859-5 | |
RU_RU | UTF8 | ||
Serbian Cyrillic | SR_SP | UTF8 | |
Serbian Latin | SH_SP | UTF8 | |
Slovak | SK_SK | UTF8 | |
sk_SK | ISO8859-2 | ||
Slovene | SL_SI | UTF8 | |
Spanish | es_ES | ISO8859-1 | yes |
es_ES | IBM-1252 | yes | |
Es_ES | IBM-850 | yes | |
ES_ES | UTF8 | yes | |
Swedish | sv_SE | ISO8859-1 | yes |
Sv_SE | IBM-850 | yes | |
SV_SE | UTF8 | yes | |
Thai | th_TH | TIS-620 | |
TH_TH | UTF8 | ||
Turkish | TR_TR | UTF8 | |
Ukrainian | UK_UA | UTF8 | |
Vietnamese | VI_VN | UTF8 |