=//========================================================================IBM= // IBM JAVA 1.1.8 README Copyright (c) 1996,1998,1999 IBM Corporation. Build date: 09 May 2002 Release name: 1.1.8 Full version: JDK 1.1.8 IBM build a118-20020509 This is the latest release of the AIX Developer Kit, Java Technology Edition, Version 1.1.8. It is based on the Sun FCS 1.1.8 Solaris code base and the IBM AIX 1.1.6 JDK release. In addition we have added the following; A version of the JDBC-ODBC bridge backported from 1.2; An optionally installable Security Migration Aid for Java backported from 1.2; A new RMI-IIOP package; A new Big Decimal class package; An enhanced JIT compiler; Plus numerous fixes engineered jointly between IBM and Sun. //-- 1. FEATURES ------------------------------------------------------------- /- Fully Java (tm) compatible - Write Once Run Anywhere /- Performance enhancements - IBM Tokyo Research Labs optimizing JIT compiler version 3.1 - "Handle-less" machine model - Fast, lightweight monitors - Thread-local heap /- Support for the new European Union currency, the Euro. See Section 10 below for more details. /- Scaling support for large numbers of threads and large numbers of file handles is better with this release. To get maximum scaling do the following: - For maximum threads (with JIT) suggest setting -ss32k as the minimum stacksize (-ss setting is 256K by default and can be as small as 16K; a smaller setting allows for a larger number of threads) - For maximum file handles use command "ulimit" or "chuser" to increase the limit ("ulimit -a" shows current limit) Note: -mx settings in excess of 512MB now work correctly /- Support for display in the sk_SK locale. //-- 2. NOTE ----------------------------------------------------------------- The software contained in this package may only be used on AIX Version 4.2.1 or later. It is NOT supported on earlier versions. This README file is part of a distribution and is applicable only to that particular distribution. Please ensure that you have the README file appropriate to the package you are using. After installation the response to 'java -fullversion' should be "JDK 1.1.8 IBM build a118-20020509". //-- 3. INSTALLATION --------------------------------------------------------- /-- 3.1. INSTALLP IMAGE After AIX installation the minimum Java installation (Java.rte) may have been completed, but you can also download a release. The installp image comes in the form of six files Java.adt Java.rte Java.samples Java.rmi-iiop Java.security Java.swing To install the Application Development Kit or the samples use the installp command or the system management GUI of your choice. The fileset names are: Java.adt.docs Java.adt.includes Java.adt.src Java.rte.Dt Java.rte.bin Java.rte.classes Java.rte.lib Java.samples.AIXDemos Java.samples.demos Java.samples.examples Java.rmi-iiop.bin Java.rmi-iiop.docs Java.rmi-iiop.lib Java.rmi-iiop.samples Java.security.docs Java.security.lib Java.swing.doc Java.swing.examples Java.swing.lib Java.swing.src The software will be installed in directory /usr/jdk_base/ Set up your PATH environment variable to refer to the new installation: export PATH=/usr/jdk_base/bin:$PATH /-- 3.2 Installation prerequisites for appletviewer to play audio on AIX For appletviewer to play audio on AIX please ensure that the following packages are installed: UMS.H_32x 2.2.0.1 COMMITTED AIX Ultimedia Services H.32x UMS.demo 2.2.0.0 COMMITTED AIX Ultimedia Services Demo UMS.html.en_US.prog_gd 4.3.0.0 COMMITTED Ultimedia Programming - U. S. UMS.html.en_US.user_gd 4.3.0.0 COMMITTED Ultimedia User Guides - U. S. UMS.loc.en_US.objects 2.2.0.0 COMMITTED Ultimedia Services Locales - UMS.msg.en_US.objects 2.2.0.0 COMMITTED AIX Ultimedia Services UMS.objects 2.2.0.1 COMMITTED AIX Ultimedia Services UMS.samples 2.2.0.0 COMMITTED AIX Ultimedia Services Samples UMS.speech 2.2.0.0 COMMITTED AIX Ultimedia Services Speech UMS.video_ext 2.2.0.1 COMMITTED AIX Ultimedia Services Video UMS.H_32x 2.2.0.0 COMMITTED AIX Ultimedia Services H.32x UMS.demo 2.2.0.0 COMMITTED AIX Ultimedia Services Demo UMS.loc.en_US.objects 2.2.0.0 COMMITTED Ultimedia Services Locales - UMS.objects 2.2.0.0 COMMITTED AIX Ultimedia Services UMS.speech 2.2.0.0 COMMITTED AIX Ultimedia Services Speech These filesets are available in bonus pack CD of AIX 4.3.1 and higher. Note: The versions of the filesets listed above can be higher depending on the AIX OS version. //-- 4. VERIFICATION --------------------------------------------------------- To ensure that the verification process behaves consistently, do the following: unset LIBPATH unset CLASSPATH unset LD_LIBRARY_PATH unset JAVA_COMPILER unset JAVA_HOME If you issue the command java -fullversion it should respond with: java full version "JDK 1.1.8 IBM build a118-20020509" If this is not correct, check that the PATH is set up correctly. (See above). Once verification is complete, relogin and review any values you may have assigned to these variables for possible conflicts with the new installation. Unless it already existed, executing 'appletviewer' will create a directory called .hotjava in your home directory. Issuing 'ls -a ~' should confirm this. //-- 5. JUST-IN-TIME (JIT) COMPILER ------------------------------------------ The JIT compiler, which speeds up execution of Java, is included in this release, and is now enabled by default. To disable the Just In Time (JIT) compiler, set the JAVA_COMPILER environment variable to "off". This can be done in one of the following ways: For the Korn shell: export JAVA_COMPILER=off For the Bourne shell: JAVA_COMPILER=off export JAVA_COMPILER For the C shell: setenv JAVA_COMPILER off Alternatively, the JAVA_COMPILER environment variable can be overridden from the command line using the -Djava.compiler option, for example: java -Djava.compiler=off - switches off the jit java -Djava.compiler= - switches on the jit It is also possible to specify a specific jit - the default is jitc. To do this set JAVA_COMPILER= or use the command line option, that is: java.compiler=. As the jit compiler is updated, we will include earlier versions of the jit with the JDK release. The current jit version is v3.0. (N.B. 1. If JAVA_COMPILER="" or java.compiler="" then the jit will be switched off. If JAVA_COMPILER is set but set to nothing or -Djava.compiler is used with no =, then the default jit is swtiched on. The default jit will always be the latest version. 2. "NONE" can be used as an alternative to "off") //-- 6. AIX NATIVE THREADS --------------------------------------------------- The JDK uses AIX's POSIX threads ('pthread') package for its threading. This means that Java threads can be scheduled on multiple processors on multi-processor systems. Thread priorities are not supported. All threads run at the same priority. The 'green threads' implementation released with JDK1.0.2 is no longer supported. Java requires all of its threads to use 'system contention scope'. The executable tools that are distributed with the JDK, java, java_g, etc., have been compiled and linked to ensure that system contention scope threads are used. However, it is possible for JNI invocation API applications, which have their own executables, to inadvertantly create and attach 'process contention scope' threads to the JVM. This can cause hangs and crashes due to signaling and GC problems with process contention scope threads and the JVM. Applications built on AIX4.3+ will use process contention scope threads by default, so explicit action needs to be taken to ensure that these applications use system contention scope threads at run-time. There are two ways to achieve this: 1. Set the environment variable 'AIXTHREAD_SCOPE=S'. This will cause all threads to be created with system contention scope by default. 2. Specify 'system scope' explicitly in the pthread attributes structure when creating a pthread to attach to the JVM. See the AIX system documentation on pthreads for more details. //-- 7. JNI EXAMPLE ---------------------------------------------------------- In the examples/jni_example directory, you will find a simple example of the use of the new JNI interface for native methods introduced in 1.1 The file jni_example/README contains information about the example, plus general notes on shared libraries. The IBM AIX Developer Kit, Java Technology Edition, Version 1.1.8 does not support runtime linking (using the -brtl loader option). Any applications built for use with the IBM AIX Developer Kit, Technology Edition, Version 1.1.8 should not rely on runtime linking functionality. Note about JNI on AIX4.3: because of some incompatibility between the JDK and some system defined types, compilation of JNI code requires that the compiler use the flag _AIX43. This flag is defined by default in /etc/ibmcxx.cfg. But, if you are using a version of xlc prior to v3.6.4 then you will need to add _AIX43 to /etc/xlC.cfg or use -D_AIX43 as a compilation command line option. Note 2 about JNI on AIX4.3+: please refer to the notes in Section 6 regarding thread-scope and JNI invocation API applications. //- 8. LARGE PROGRAM MODEL SUPPORT The JVM of The IBM AIX Developer Kit, Java Technology Edition, Version 1.1.8 can support large program model. For more details on large program model, see: http://www.rs6000.ibm.com/doc_link/en_US/a_doc_lib/aixprggd/genprogc/larg_prg_support.htm The 1.1.8 JVM's launcher executables (java, java_g, jre and jre_g) are built to use the default small memory model. This limits the memory available to malloc() etc., which in turn limits the number of threads running simultaneously. While the small memory model should prove adequate for most java applications, there are likely to be some heavyweight applications which require the large memory model to support large native structures, or large numbers of threads. There are 3 ways to enable java and your application to support the large program model: - You can patch the binary executable with the following shell command which allows the program "app" to access up to 8 segments (where each segment is 256MB): /usr/bin/echo '\0200\0\0\0'|dd of="app" bs=4 count=1 seek=19 conv=notrunc Using values of '\0120\0\0\0' or '\0100\0\0\0" would enable the use of 5 or 4 segments of data heap, respectively. - You can link the program with the -bmaxdata:0x80000000 flag. - For AIX 4.3.3.10 or later, you can override the maxdata setting for an executable with the LDR_CNTRL environment variable: export LDR_CNTRL=MAXDATA=0x80000000 If your application uses a lot of functions like shmat() and mmap(), or if you attach shared memory to fixed addresses in your application, you will not want to allocate all 8 segments for the data heap. Use a smaller setting to suit your application. //-- 9. AIX FIXES ------------------------------------------------------------ There are AIX bugs that occurs in certain versions which may affect Java. 1. In version 4.2.0.0 there is a problem with the thread-safe function gethostbyaddr_r. It returns an empty string. This has been worked around in JDK1.1.2 and later versions, but the workaround is not entirely thread-safe, so it may fail in thread-intensive applications. To rectify the problem, you need to upgrade the following filesets to these levels: bos.rte.libc 4.2.0.7 bos.rte.libnetsvc 4.2.0.1 bos.rte.libs 4.2.0.5 bos.rte.security 4.2.0.7 bos.up 4.2.0.12 You can check the current level of bos.rte.libc with this command: lslpp -ah bos.rte.libc The easiest way to upgrade is using the FixDist tool, available from: http://service.software.ibm.com/cgi-bin/support/rs6000.support/downloads FixDist allows the user to select and download fixes based on fileset level (as above), as well as APAR number. 2. In version 4.3.* there can be some problems with version 4.0.0.* of the xlC libraries. These manifest themselves as failures at JVM shutdown, with stack traces (see javacores, dbx the core file or in "errpt -a" output) of the form:- signal.pthread_kill signal._p_raise raise.raise abort.abort _Getcat__Q2_3std8messagesXTw_FPPCQ3_3std6locale5facet terminate__3stdFv terminate__Fv except.__DoThrow __dt__12__short_lockFv __sterm_x_2fu_5fC_2b_2b_2fmcnamara_2fusltusc299_2fstream_2fstream_2ec__Fi terminate_orig_libs__Fv cuexit.exit sysExit To fix this, apply the 5.0.0.4 libraries as indicated by APAR IY14529:- The base level filesets for the 5.0 C++ Runtime are at http://www-4.ibm.com/software/ad/vacpp/service/csd.html#redistribute To find the latest C++ runtime PTFs search for APAR IY14529 on http://techsupport.services.ibm.com/support/rs6000 under "SW Fix Database by APAR". //-- 10. SUPPORTED LOCALES & how to run programs in different locales --------- **N.B. The encoding for some locales has changed at PTF4. A full list of the changes appears below. ***N.B. An alternative fonts.properties.zh file has been made available for zh_CN locale for AIX 4.3.3 and above at PTF5 . The new file enables new fonts, but requires special instalation. Details appear below. To run in a locale other than the default, you must first have the locale fully installed. You can use the SMIT tool (System Environments/Manage Language Environment) to install a new locale. You can check the installed locales with the `locale -a` command. Then, you must set the LC_ALL and LANG environment variables, for example to run in Japanese, use the following (in Korn Shell): export LC_ALL=JA_JP export LANG=JA_JP java MyProgram IMPORTANT: The locales listed in the 'AIX LOCALE' column below are the ONLY ones supported by Java. So, if you need to use the EUC encoding of Japanese, you MUST set LC_ALL and LANG to 'ja_JP', NOT to 'ja_JP.IBM-eucJP'. Similarly, any 'long' locale names not listed in the table below are NOT supported by Java. Also note that the long names currently supported (such as Ja_JP.IBM-932) are present purely for temporary backwards compatability and may be phased out in the future. We also recommend you use the new UTF8 locales where possible, for example JA_JP rather than ja_JP. The 'TRANSLATIONS' column indicates the locales which have native language messages for java. If there are no translations, all messages will be in English. LANGUAGE AIX LOCALE ENCODING TRANSLATIONS ====== ========== ======== ============ Albanian SQ_AL UTF8 Arabic AR_AA UTF8 Bulgarian bg_BG ISO8859-5 BG_BG UTF8 Byelorussian BE_BY UTF8 Catalan ca_ES ISO8859-1 ca_ES.IBM-1252 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 IBM-1252 Nl_BE IBM-850 NL_BE UTF8 Dutch nl_NL ISO8859-1 nl_NL.IBM-1252 IBM-1252 Nl_NL IBM-850 NL_NL UTF8 English (Great Britain) en_GB ISO8859-1 yes En_GB IBM-850 yes EN_GB UTF8 yes English (United States) en_US ISO8859-1 yes En_US IBM-850 yes EN_US UTF8 yes Estonian ET_EE UTF8 Finnish fi_FI ISO8859-1 fi_FI.IBM-1252 IBM-1252 Fi_FI IBM-850 FI_FI UTF8 French (Belgium) fr_BE ISO8859-1 yes fr_BE.IBM-1252 IBM-1252 yes Fr_BE IBM-850 yes FR_BE UTF8 yes French (Canada) fr_CA ISO8859-1 yes Fr_CA IBM-850 yes FR_CA UTF8 yes French fr_FR ISO8859-1 yes fr_FR.IBM-1252 IBM-1252 yes Fr_FR IBM-850 yes FR_FR UTF8 yes French (Switzerland) fr_CH ISO8859-1 yes Fr_CH IBM-850 yes FR_CH UTF8 yes German de_DE ISO8859-1 yes de_DE.IBM-1252 IBM-1252 yes De_DE IBM-850 yes DE_DE UTF8 yes German (Switzerland) de_CH ISO8859-1 yes De_CH IBM-850 yes DE_CH UTF8 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 IBM-850 IS_IS UTF8 Italian it_IT ISO8859-1 yes it_IT.IBM-1252 IBM-1252 It_IT IBM-850 yes IT_IT UTF8 yes Japanese ja_JP IBM-33722C yes Ja_JP (AIX < 4.3.2) IBM-942C yes Ja_JP (AIX >= 4.3.2) IBM-943C yes Ja_JP.IBM-932 IBM-942C yes Ja_JP.IBM-943 IBM-943C 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 IBM-850 NO_NO UTF8 Polish pl_PL ISO8859-2 PL_PL UTF8 Portuguese (Brazil) pt_BR ISO8859-1 yes Pt_BR IBM-850 yes PT_BR UTF8 yes Portuguese pt_PT ISO8859-1 pt_PT.IBM-1252 IBM-1252 Pt_PT IBM-850 PT_PT UTF8 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 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 UTF8 Turkish TR_TR UTF8 Ukrainian UK_UA UTF8 Vietnamese VI_VN UTF8 ** The following changes were made at PTF4 AIX LOCALE PREVIOUS ENCODING CURRENT ENCODING ========== ================= ================ ja_JP eucJIS IBM-33722C Ja_JP JIS IBM-942C/IBM-943C Ja_JP.IBM-932 IBM-942 IBM-942C Ja_JP.IBM-943 IBM-943 IBM-943C The changes allow java to translate the IBM entended kanji's, and also fix javac compilation problems due to backslash/yen translations. Note that for locale Ja_JP, the encoding used depends on the AIX operating system level. For this locale on AIX 4.3.1 and earlier, IBM-942C is used, but on AIX 4.3.2 and later, IBM-943C is used. This matches the change made to the native encoding for the Ja_JP locale at AIX 4.3.2. *** New zh_CN font support at PTF5 Java by default uses the 17 point fonts -ibm_aix-song-medium-r-normal--*-%d-*-*-m-*-*-* in zh_CN locale. This font is large (17-point) which can cause problems with AWT layout. On AIX 4.3.3 the 13-pt fonts -monotype-sansmonowt-medium-r-normal--*-%d-*-*-m-*-*-* are available. To check whether your system has the new fonts, go to directory /usr/lib/X11/fonts/, and issue the command: > grep monotype-sansmonowt- fonts.dir You should see output containing the lines: gb18tt.pcf.Z -monotype-sansmonowt-medium-r-normal--18-130-100-100-m-90-gb2312.1980-0 rom9tt.pcf.Z -monotype-sansmonowt-medium-r-normal--18-130-100-100-m-90-iso8859-1 If these lines do not appear, then the new fonts are not available on your system. To enable use of the new fonts in java, go to the /lib directory and issue the following commands: > mv font.properties.zh font.properties.zh.orig > cp font.properties.zh.4.3.3 font.properties.zh In order to restore the original settings, restore the original file as follows: > cp font.properties.zh.orig font.properties.zh Note that when displaying on an X server on a remote machine, the remote machine should also support the new fonts. //-- 11. EURO SUPPORT -------------------------------------------------------- Support for the new European Union currency, the Euro, is included in the JDK. Platform-level support is required to make use of this, as follows: On AIX 4.3.2 (and upwards) the Euro is supported via the new UTF8 locales. This is the primary mechanism for Euro support on AIX. On AIX 4.2.1 the Euro is supported via the "Single Byte Euro Migration Option" which is available as APAR IX83167. This adds the Euro to IBM-1252 encodings of the following locales: ca_ES, de_DE, fr_FR, es_ES, fi_FI, fr_BE, nl_NL, nl_BE, pt_PT, and it_IT. After installing the patch, and restarting your X server, you need to set the LANG and LC_ALL environment variables to the full locale, for example "de_DE.IBM-1252", and then start a dtterm, so that it uses the correct fonts. There is no Euro support on any older versions of AIX. With either of the above options, applications can then make use of the Euro symbol (using Unicode character '\u20AC') and Euro variants of Java Locales, which provide the appropriate currency formatting. The environment variable LC_MONETARY is currently not used by Java - the default is always the national currency. To get a Euro currency locale each application needs to create a "EURO" variant of a Java Locale. For more information on IBM's position on the Euro currency, see: http://www.ibm.com/euro //-- 12. JDBC-ODBC BRIDGE ---------------------------------------------------- An edition of JDBC-ODBC Bridge is backported from JDK 1.2 to JDK 1.1.x. Security Model for the Bridge remains unchanged as for JDK 1.1.x. JNI Interface is used in this AIX version. This verion assumes that your ODBC driver can support concurrency and you are expected to provide locking in your application if necessary. In the examples/jdbcodbc_example directory, you will find a sample Java program using the JDBC-ODBC Bridge to connect to a target database. A C sample program is also provided for you to test your direct ODBC connection. 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. The file jdbcodbc_example/README contains information about the sample programs and also information on how to set up the environment to use the JDBC-ODBC Bridge. //-- 13. ENHANCED BIGDECIMAL CLASS ------------------------------------------- This release introduces an enhanced BigDecimal class (com.ibm.math.BigDecimal) for Java, which is provided as an alternative for java.math.BigDecimal. The new class (and its supporting class MathContext) is fully implemented and exploits interface java.lang.Comparable which is used for sorting in Java 2, This interface is included in the classes provided with this enhancement, renamed as com.ibm.math.java.lang.Comparable. If you already use that BigDecimal class, you can probably simply change the import statement: import java.math.*; to import com.ibm.math.*; to access the new class without changing any other code. The new class is available in /usr/jdk_base/lib/math.jar and the .java_wrapper script is updated to include this jar file at the end of the CLASSPATH environment variable. If you launch your java programs differently, then you need to add this jar file into your own CLASSPATH. API documentation is included in the /usr/jdk_base/bigdecimal/docs directory. A small example program decdemo.java and README.dec are available in the /usr/jdk_base/examples/bigdecimal directory. //-- 14. RMI-IIOP ------------------------------------------------------------ Also packaged with this release is an extension to support RMI over IIOP. This allows RMI applications to communicate using the IIOP protocol and interoperate with CORBA applications written in any language. The runtime support for RMI-IIOP is packaged within Java.rte. The .java_wrapper script is updated to include the RMI-IIOP runtime at the end of the CLASSPATH. The developer support is in the optional Java.rmi-iiop package. When you install the RMI-IIOP developer support, you replace rmic with a new version which supports the generation of IIOP stubs and ties, and is backward- compatible for JRMP. See the RMI-IIOP readme (/usr/jdk_base/rmi-iiop/readme.html) for detailed information. //-- 15. Security Migration Aid ---------------------------------------------- Also packaged with this release is an optionally installable Security Migration Aid for Java. The Security Migration Aid allows users of IBM's Java Development Kit (JDK) version 1.1.8 to exploit enhancements in the Java security model defined in Java 1.2 without having to use a 1.2 version of the Java JDK. The Security Migration Aid is intended to help users who wish to migrate from the, relatively simple, Java 1.1 security model to the finer grained Java 1.2 model. The Security Migration Aid features support the use of security policies, permissions, tools and java runtime security managers as defined in the Java 1.2 security model. Applet development using features of the 1.2 security model is supported and the Security Migration Aid includes an applet viewer that implements the expected security policies and checks as defined by the user. The Security Migration Aid consists of new, security related Java classes, packaged by IBM (in com.ibm.security12 and optionally installable) but that appear functionally like their Java 1.2 equivalents. These IBM classes run in the JDK 1.8 environment together with some additional supporting classes and native code. Applications, applets and data files can make use of Java 1.2 security features without the need for users to develop equivalent, fine grained, security mechanisms and resulting in systems that are more easily ported to a Java 1.2 environment. The Migration Aid is optionally installable from the material in /usr/jdk_base/security and once installed will place a jar file containing the Security Migration Aid Classes (SecMA.jar) in the directory alongside the JDK classes.zip file and a native shared library (libSecMA.a) alongside the core JDK's shared libraries in /usr/jdk_base/lib/aix/native_threads. Once installed, the Security Migration Aid's features can be used by placing its jar file (/usr/jdk_base/lib/SecMA.jar) AHEAD of the standard JDK classes in the classpath. The install process additionally places some example security configuration files alongside the original JDK security.java file in /usr/jdk_base/lib/security/ that can be used as templates for configuration of a Migration Aid security policy. Additional documentation can be found in the /usr/jdk_base/security/docs directory once the Security Migration Aid documentation is installed. A more detailed version of this README information for the Security Migration Aid is installed to /usr/jdk_base/security/README.SecMA when the Security Migration Aid is installed. //-- 16. JAVACORE.TXT --------------------------------------------------- In the unfortunate event of a core dump in your application when using JDK 1.1.8, you will get a javacore text file in addition to the core file. At service refresh 10 and above, the javacore file has a filename of the format of javacore.