________________________________________________________________________ OS/2 Warp Developer's Kit for Java(TM) 1.1.6 Installation README ________________________________________________________________________ OS/2 Warp Developer's Kit for Java(TM) 1.1.6 provides the Sun Microsystems, Inc. Java environment on: OS/2 Warp 4 OS/2 Warp Server Version 4 OS/2 Warp Server Advanced Version 4 OS/2 Warp Server Advanced Version 4 SMP Feature WorkSpace On-Demand clients and servers OS/2 Warp Version 3 OS/2 Warp Connect References in this README to OS/2 Warp 4 refer to the OS/2 Warp 4 client operating system and the WorkSpace On-Demand client. OS/2 Warp Server is used to refer to all of the OS/2 Warp Server operating systems and the WorkSpace On-Demand server. References to OS/2 Warp 3 refer to OS/2 Warp Version 3 and OS/2 Warp Connect. This README guides you through installation of OS/2 Warp Developer's Kit for Java 1.1.6 (also referred to in this README as Java 1.1.6) and provides information about known problems and temporary fixes for them. ________________________________________________________________________ CONTENTS 1. Before You Install 1.1 Disk Space Requirements 1.2 Software Prerequisites 1.2.1 FixPak Required on OS/2 Warp 3 Systems 1.2.2 OS/2 Warp Server and Warp 3 Systems Require FixPak for Unicode Font Support 1.2.3 FixPak Required for Eurocurrency Symbol Support 1.2.4 Feature Install Required for Installing Java 1.1.6 1.3 HPFS and FAT Partition Considerations 1.4 Coexistence with Prior Versions of Java 1.4.1 Coexistence with Java 1.0.1 and 1.0.2 1.4.2 Replacing Previous Versions of Java 1.1.x 1.5 Backing Up Base OS/2 Files Not Restored during Uninstallation 1.6 Making a Copy of Your Current CONFIG.SYS File 1.7 Minimum Hardware Recommendations 1.8 Installing FixPaks on OS/2 Warp 4 Systems after Java 1.1.6 1.9 Installation Panel Text Missing or Too Long in DBCS Countries 1.10 Installing on OS/2 Warp 4 Japanese version (without VoiceType) 1.11 Japanese Environment Settings on OS/2 Warp 4 Japanese version 1.12 Required Fonts on OS/2 Warp Japanese version 2. Installing OS/2 Warp Developer's Kit for Java 1.1.6 2.1 Installing OS/2 Warp Developer's Kit for Java 1.1.6 through the Graphical User Interface (GUI) 2.1.1 Desktop Method 2.1.2 OS/2 Command Prompt Method 2.1.3 Selections Grayed during Installation 2.1.4 Recovering from a Failed Installation 2.1.5 Unable to Create Feature Install Object on OS/2 Warp Server and OS/2 Warp 3 Systems 2.2 Unattended (CID) Installation Method 2.2.1 Modifying the CID Response File 2.2.2 Starting the Unattended Installation 2.2.3 Performing an Unattended Uninstallation 2.3 TME-Architected CID Installation Method 2.4. NetView DM/2 (NVDM/2) Installation Considerations 2.4.1 Put Static Command in NVDM/2 Profile 2.4.2 Customize JAVA116.RSP File 2.5 Remote IPL Installation Considerations 2.5.1 Creating Response Files 2.5.2 Modifying the JAVA116.RSP File 2.5.3 Updating Files for Feature Install 2.5.4 Starting the Remote IPL Installation 2.5.5 Running the Java Samples from a Remote IPL Client 2.5.6 Upgrading Java 1.1.4 to Java 1.1.6 in the Remote IPL Environment 2.5.7 Remote IPL Restrictions 2.6 Installing OS/2 Warp Developer's Kit for Java 1.1.6 on WorkSpace On-Demand 2.6.1 Installing OS/2 Warp Developer's Kit for Java 1.1.6 for Use on a WorkSpace On-Demand Server 2.6.2 Installing OS/2 Warp Developer's Kit for Java 1.1.6 for a WorkSpace On-Demand Client 2.6.2.1 Requirements for Installation on a WorkSpace On-Demand Client 2.6.2.2 Modifying the CID.CMD and WSOD.RSP Files 2.6.2.3 Installing Additional Java 1.1.6 Components on the WorkSpace On-Demand Client 2.6.3 Uninstalling from WorkSpace On-Demand 3. Uninstalling OS/2 Warp Developer's Kit for Java 1.1.6 3.1 Desktop Method 3.2 OS/2 Command Prompt Method 3.3 Restoring Base OS/2 Files 3.4 State of CONFIG.SYS File After Uninstalling Java 1.1.6 3.5 Entries Left in CONFIG.SYS after Uninstalling Toolkit Component 3.6 Unattended Uninstallation 3.7 Uninstalling on WorkSpace On-Demand 4. After You Install 4.1 Additional Sources of Information 4.2 Installing Additional Components 4.3 Starting a Java Application that Calls a Non-Presentation Manager Program 4.4 Disabling the Just-In-Time (JIT) Compiler 4.5 Native Methods Need to be Recompiled 4.6 LIBPATH Changes That Could Affect Your System 4.7 Timer Resolution 4.8 Applying OS/2 Service after Installing OS/2 Warp Developer's Kit for Java 1.1.6 4.9 Installing a FixPak on OS/2 Warp Server or OS/2 Warp 3 Systems after Java 1.1.6 4.10 Using 16-Color Mode with OS/2 Warp Developer's Kit for Java 1.1.6 4.11 JDBC-ODBC Bridge Not Provided 4.12 AWT TextField and TextArea Considerations 4.13 Controlling Arabic Number Character Display 4.14 Modifying Font Properties Files Not Supported 4.15 Printing Considerations 4.16 Backslash and Tilde Characters in DBCS Countries 4.17 Using Java 1.0.2 for OS/2 after Installing OS/2 Warp Developer's Kit for Java 1.1.6 4.18 Problems with Time in Java Applets 4.19 Korean OS/2 Users Need PTF for Updated Fonts 4.20 TrueType Fonts Must Be Installed on Chinese Systems 4.21 Conversion between ShiftJIS and Unicode on OS/2 Warp 4 Japanese version 4.22 Installing Japanese FixPak 2 (FX00002) over OS/2 Warp 4 Japanese version (without VoiceType) and Java 1.1.6 5. List of OS/2 Base Modules Changed or Added by OS/2 Warp Developer's Kit for Java 1.1.6 6. Trademarks ________________________________________________________________________ 1. Before You Install Note: In this document, the term partition refers to any physical or logical drive. ____________________________ 1.1. Disk Space Requirements OS/2 Warp Developer's Kit for OS/2 Warp consists of the following components: Runtime, including Internationalization Support 11.0 MB Times New Roman MT 30 Unicode Font 13.0 MB Toolkit 3.0 MB Toolkit Documentation 8.0 MB Samples 3.0 MB ICAT Debugger for OS/2 Java 14.0 MB ______________________ _______ Total installed size 52.0 MB For convenience, three separate downloadable packages (separate ZIP files) are provided. You can download: - The runtime package, which contains the Runtime component and the JIT compiler. The runtime package allows you to run Java applets and applications. - The runtime package, which contains the Runtime component, the JIT compiler, and the Unicode Font. You need this runtime package rather than the first one if you use multiple languages on a single system or if you use a double-byte character set (DBCS) language. - The development package, which contains the Toolkit, Toolkit Documentation, Samples, and the ICAT Debugger. This package allows you to develop Java applets and applications. The Runtime component must be installed to use any component other than Toolkit Documentation. The Times New Roman MT 30 Unicode Font component can be installed on OS/2 Warp 4 systems. OS/2 Warp Server and OS/2 Warp 3 systems must be at a FixPak 30 service level or higher to install the Unicode Font component. Ensure that sufficient disk space is available before installing. Note: Be sure that when you extracted the OS/2 Warp Developer's Kit for Java 1.1.6 files from the original ZIP files, you specified the proper option on your file extraction utility to create subdirectories. For pkunzip2 this option is -d. Failure to extract the files properly results in the installation program failing while copying files. If you did not use this option, you should extract the files again before you install. The different packages contain some identical files. To save time and effort if you are extracting more than one package, use the option on your extraction utility that overwrites existing files without prompting. For pkunzip2, this option is -o. If you do not use the option, you will be asked, for each duplicate file, whether you want to overwrite that file. Because the files are identical, it makes no difference whether you answer Yes or No. ___________________________ 1.2. Software Prerequisites _____________________________________________ 1.2.1. FixPak Required on OS/2 Warp 3 Systems To use OS/2 Warp Developer's Kit for Java 1.1.6 on an OS/2 Warp 3 system, apply FixPak 32 or higher for single-byte character set (SBCS) languages. For Japanese, Korean, or Traditional Chinese, apply FixPak WX03006. For Simplified Chinese, apply FixPak FX03006. For information about downloading a particular FixPak, contact your local IBM OS/2 support representative. If you choose to install the FixPak after installing OS/2 Warp Developer's Kit for Java 1.1.6, be sure to read sections 4.8 and 4.9 of this README. _____________________________________________________________________ 1.2.2. OS/2 Warp Server and Warp 3 Systems Require FixPak for Unicode Font Support If you want to use the Unicode Font support on an OS/2 Warp Server Server or OS/2 Warp 3 system, you should first apply FixPak 30 (or higher) for single-byte character set (SBCS) languages. For Japanese, Korean, or Traditional Chinese, apply FixPak WX03006. For Simplified Chinese, apply FixPak FX03006. To obtain access to download a particular FixPak, contact your local IBM OS/2 support representative. If you choose to install the FixPak after installing OS/2 Warp Developer's Kit for Java 1.1.6, be sure to read sections 4.8 and 4.9 of this README. _______________________________________________________ 1.2.3. FixPak Required for Eurocurrency Symbol Support If you want to use the Eurocurrency symbol in Java applications and applets on an OS/2 Warp 4 system, apply FixPak 6 or higher. For Eurocurrency symbol support on OS/2 Warp Server or OS/2 Warp 3 systems, apply FixPak 35 or higher. For information about downloading a particular FixPak, contact your local IBM OS/2 support representative. If you choose to install the FixPak after installing OS/2 Warp Developer's Kit for Java 1.1.6, be sure to read sections 4.8 and 4.9 of this README. _________________________________________________________ 1.2.4. Feature Install Required for Installing Java 1.1.6 OS/2 Feature Install is used to install OS/2 Warp Developer's Kit for Java 1.1.6, whether you are installing on a local system or on a remote system using an unattended CID or remote IPL install. Version 1.2 or higher of OS/2 Feature Install is required. You can obtain the latest version of Feature Install from the IBM Software Choice Web site at: http://www.software.ibm.com/os/warp/swchoice/ ___________________________________________ 1.3. HPFS and FAT Partition Considerations The Runtime and ICAT Debugger components can be installed on a FAT partition. However, for better performance, install them on an HPFS partition, which supports long file names. The Toolkit, Toolkit Documentation, and Samples components must be installed on an HPFS partition. The Internationalization Support portion of the Runtime component and the Times New Roman MT 30 Unicode Font component are installed on the boot partition. If you use the Guided Install path, all components must reside on the same partition. Use Advanced Install to select specific drives and directories for the different components. Note: If you have only one hard disk with a single FAT partition, you have three options: - Leave your system as it is and install only the Runtime component and, optionally, the ICAT Debugger component. - Format the FAT partition for HPFS and reinstall all software. - Purchase a disk partitioning program, such as PartitionMagic. With sufficient space, a disk partitioning program reduces the size of the current partition (drive C) and creates a new partition (logical drive D), which can be formatted for HPFS. _____________________________________________ 1.4. Coexistence with Prior Versions of Java OS/2 Warp Developer's Kit for Java 1.1.6 replaces all previous versions of Java 1.1.x for OS/2 Warp and coexists with Java 1.0.x. ____________________________________________ 1.4.1. Coexistence with Java 1.0.1 and 1.0.2 The 1.0.x versions of Java are installed in a \JAVAOS2 directory. The installation program, by default, installs OS/2 Warp Developer's Kit for Java 1.1.6 in a \JAVA11 directory, which allows the two versions of Java to coexist on the system. Do not install Java 1.1.6 into the \JAVAOS2 directory. If you overlay the files in the \JAVAOS2 directory, Java applets that run in Netscape Navigator for OS/2 no longer work, and uninstalling OS/2 Warp Developer's Kit for Java 1.1.6 leaves the system without Java support. Java applications and applets that are run from an OS/2 Command Prompt or launched from the Desktop use OS/2 Warp Developer's Kit for Java 1.1.6. The use of Java 1.0.2 for OS/2 outside Netscape Navigator for OS/2 is not supported after OS/2 Warp Developer's Kit for Java 1.1.6 has been installed. ________________________________________________ 1.4.2. Replacing Previous Versions of Java 1.1.x If an earlier version of Java 1.1.x is installed on your system, you must either uninstall it before you install Java 1.1.6 or replace Java 1.1.x by installing Java 1.1.6 over (in the same directory as) Java 1.1.x. If you plan to install fewer components of Java 1.1.6 than you currently have on your system from a previous installation of Java 1.1.x, you should uninstall the components that you will not be replacing before you install Java 1.1.6. If you attempt to install Java 1.1.6 in such a way that you have components from different versions of Java 1.1.x, you receive warning messages during installation. ___________________________________________________________________ 1.5. Backing Up Base OS/2 Files Not Restored during Uninstallation OS/2 Warp Developer's Kit for Java 1.1.6 updates base operating system modules as part of the installation of the Runtime component. Uninstalling OS/2 Warp Developer's Kit for Java 1.1.6 does not restore the original versions of these files. In most cases, you do not need to restore the previous versions of these files. If you want the ability to restore these files, you must make copies of them before you install. Be sure to record the location of the copied files so that you can restore them if necessary. A complete list of new and changed base modules is included in section 5 of this README. ___________________________________________________ 1.6. Making a Copy of Your Current CONFIG.SYS File Before installing OS/2 Warp Developer's Kit for Java 1.1.6, make a copy of your current CONFIG.SYS file. This ensures that you can return to your original environment if problems occur during installation. ______________________________________ 1.7. Minimum Hardware Recommendations A minimum of 32 MB of random access memory (RAM) provides the best results when running OS/2 Warp Developer's Kit for Java 1.1.6 applications and applets. Use an Intel(R) 486 processor or higher for OS/2 Warp 4 clients and OS/2 Warp 3 systems. Use an Intel Pentium(R) processor or higher for OS/2 Warp Server systems. ________________________________________________________________ 1.8. Installing FixPaks on OS/2 Warp 4 Systems after Java 1.1.6 If you want to install a FixPak prior to FixPak 6 on an OS/2 Warp 4 system after you have installed OS/2 Warp Developer's Kit for Java 1.1.6, make sure that the following files remain as they are before the FixPak is installed: CLIFI.EXE INSTALL.DLL LIBUNI.DLL UCONV.DLL You can do this by using SERVICE.EXE to install the FixPak and select not to update the files during installation of the FixPak. As an alternative, you can use another method to install the FixPak. If you use another method, do one of the following: - Save the files and then replace them after installing the FixPak. - Reinstall Feature Install and Java 1.1.6 after installing the FixPak. ___________________________________________________________________ 1.9. Installation Panel Text Missing or Too Long in DBCS Countries When installing OS/2 Warp Developer's Kit for Java 1.1.6 on DBCS versions of OS/2, DBCS characters might not be displayed on the installation panels or the lines could exceed the right border of the display window, even when the window is maximized. To correct these problems, exit the installation program, open the Netscape Navigator for OS/2 object, and select the Options menu item. Open the General Preferences notebook and select the Fonts tab. Choose the proper encoding for your country and then set the proportional and fixed fonts to MINCHO. Press OK to save the changes. When you start the installation of OS/2 Warp Developer's Kit for Java 1.1.6 again, the text should be displayed correctly. ____________________________________________________________________ 1.10. Installing on OS/2 Warp 4 Japanese version (without VoiceType) If you plan to install Japanese FixPak 2 (FX00002) over OS/2 Warp 4 Japanese version (without VoiceType), you should do it before installing OS/2 Warp Developer's Kit for Java 1.1.6. Otherwise, OS/2 may not reboot. If this occurs, see section 4.22 of this README. ___________________________________________________________________ 1.11. Japanese Environment Settings on OS/2 Warp 4 Japanese version Use the following Japanese environment settings for OS/2 Warp 4 Japanese version: Codepage 932 ShiftJIS code New JIS __________________________________________________ 1.12. Required Fonts on OS/2 Warp Japanese version To run OS/2 Warp Developer's Kit for Java 1.1.6, the following fonts are required on your system: Name Style ------------------------------------------ GOTHIC Normal GOTHIC HeiseiKakuGothic-W5-H-90-TT MINCHO HeiseiMincho-W3-H-90-TT You can check them in the Font Palette, which is in the System Setup folder in the OS/2 System folder. GOTHIC Normal font is included in GOTHIC system Japanese font. GOTHIC HeiseiKakuGothic-W5-H-90-TT is IBM HeiseiKakuGothic TrueType font with New JIS order. MINCHO HeiseiMincho-W3-H-90-TT is IBM HeiseiMincho TrueType font with New JIS order. These fonts can be installed through the Selective Install program object, which is in: - The Install/Remove folder in the System Setup folder on OS/2 Warp 4 systems - The System Setup folder on OS/2 Warp Server and OS/2 Warp 3 systems. ______________________________________________________ 2. Installing OS/2 Warp Developer's Kit for Java 1.1.6 OS/2 Warp Developer's Kit for Java 1.1.6 is provided in three separate downloadable packages: - The runtime package - The runtime package with the Unicode Font - The development package See Section 1.1 for more information about each of the packages. Keep in mind the following points before you start to install: - Be sure to download and extract all the packages you will need before you begin the installation. - Always keep all the Java 1.1.x components at the same level. For example, you should not have a Java 1.1.6 Runtime component and a Java 1.1.4 Toolkit component from an earlier installation on the same machine. - You cannot install the Toolkit, Samples, or ICAT Debugger unless you are also installing the Runtime component or you have already installed the Runtime component. - If you use the Graphical User Interface, components that you have not downloaded and extracted are grayed and cannot be selected for installation. The sections that follow tell you how to install OS/2 Warp Developer's Kit for Java 1.1.6 using different methods. _____________________________________________________________________ 2.1. Installing OS/2 Warp Developer's Kit for Java 1.1.6 through the Graphical User Interface (GUI) To install OS/2 Warp Developer's Kit for Java 1.1.6 through the GUI, use one of the following methods: ______________________ 2.1.1. Desktop Method To install using the INSTALL.EXE object, follow these steps: 1. Open the OS/2 System folder. 2. Open the Drives object. 3. Open the drive where the Java files were extracted. 4. Open the folder where the Java files were extracted. 5. Select the INSTALL.EXE object to start the install program. The installation program leads you through the installation steps. A Java 1.1.6 for OS/2 folder is created in the Programs folder on OS/2 Warp 4 systems and on the Desktop on OS/2 Warp Server and OS/2 Warp 3 systems. After the installation is complete, if you want to clean up the directory in which the Java files were extracted, select the DELINST.CMD object to remove the Java files and subdirectories from the directory where they were extracted. Files and subdirectories not extracted from the Java 1.1.6 package are not erased. __________________________________ 2.1.2. OS/2 Command Prompt Method To start installation, make sure that you are in the directory where the OS/2 Warp Developer's Kit for Java 1.1.6 files were extracted. At an OS/2 command prompt, type: install The installation program leads you through the installation steps. A Java 1.1.6 for OS/2 folder is created in the Programs folder on OS/2 Warp 4 systems and on the Desktop on OS/2 Warp Server and OS/2 Warp 3 systems. Optionally, if you want to remove the Java files and subdirectories from the directory where they were extracted, make sure that you are in the directory where the OS/2 Warp Developer's Kit for Java 1.1.6 files were extracted. At an OS/2 command prompt, enter: delinst Files and subdirectories not extracted from the Java 1.1.6 package are not erased. _____________________________________________ 2.1.3. Selections Grayed during Installation If you are using the GUI to install Java 1.1.6 and components are grayed that you believe you downloaded and extracted, you might not have downloaded and properly extracted all the ZIP files you need. Be sure that you have downloaded all the packages you need. Also, be sure that when extracting files from the ZIP files, you specify the proper options on your file extraction utility to create subdirectories. For pkunzip2 this option is -d. If the files were not extracted properly, extract them again. Because the three packages contain some duplicate files, you can save time by specifying the option on your extraction utility that overwrites existing files without prompting. For pkunzip2, this option is -o. If you do not use the option, you will be asked, for each duplicate file, whether you want to overwrite that file. Because the files are identical, it makes no difference whether you answer Yes or No. _____________________________________________ 2.1.4. Recovering from a Failed Installation If your installation of OS/2 Warp Developer's Kit for Java 1.1.6 fails, check for and delete any remaining installation objects. If you do not delete these installation objects, future installations could fail with a message stating that one or more components could not be installed because the object is read-only or in use by another process. The icon for the installation object shows a blue box with a red ribbon and is located on the Desktop for a CID install. For an attended installation, the object is in the x:\os2\install folder. To delete the object, select the object with the right mouse button and select Delete from the menu. Alternately, go to the directory containing the object, and delete the entire directory tree. The directory is named either "Install object" or "Java 1.1 for OS!2" depending on when the installation failed. After deleting the installation object, shut down and restart the system. ___________________________________________________________________ 2.1.5. Unable to Create Feature Install Object on OS/2 Warp Server and OS/2 Warp 3 Systems If your installation of OS/2 Warp Developer's Kit for Java 1.1.6 fails on an OS/2 Warp Server or OS/2 Warp 3 system and you receive a message that the program was unable to locate or create a Feature Install object, or that it could not find the response file, shut down and restart the system and run the installation program again. This problem was addressed by OS/2 APAR PJ24851. The fix for the problem is included in FixPaks 33 and higher. __________________________________________ 2.2. Unattended (CID) Installation Method Unattended or CID installations of OS/2 Warp Developer's Kit for Java 1.1.6 are handled by CLIFI, the command-line interface to Feature Install, and can take 15 to 20 minutes or more. After the installation program finishes, the system must be restarted to complete the installation. CLIFI requires two response files: the OS/2 Warp Developer's Kit for Java 1.1.6 response file, JAVA116.RSP, and a secondary response file where users can override the default selections. The CID.RSP file is included in the installation package as an example of the customized response file; this is the only file that needs to be modified for unattended installations. Feature Install version 1.2 or higher is required for CID installations. See section 1.2.3 of this README for details. ______________________________________ 2.2.1. Modifying the CID Response File The CID.RSP response file contains variables that allow you to select which components to install and the target drive and directory for each component, where appropriate. The component names are: Runtime - Java Runtime Unicode - Internationalization Support, part of Java Runtime Environment Toolkit - Toolkit TlktDoc - Toolkit Documentation Samples - Samples Debugger - OS/2 ICAT Debugger for Java Unifont - Times New Roman MT 30 Unicode Font TTengine - Updated TrueType engine, required for the Unicode Font The CID.RSP file is originally set to install all components. Modify it to install the components you want to install. Be sure that you have downloaded and extracted all the files you need. In the CID.RSP file, set "selection=1" for each component you want to install, and set "selection=0" for each component you do not want to install. Note: There is now a config component associated with each installable component. The config selection variable for each component must always be set to the same value as the selection variable for the component. For example, if you set toolkit.selection=0, you must also set toolkitconfig.selection=0. The Runtime component is always installed in the \JAVA11 directory on the target drive and is a prerequisite for the Toolkit, Samples, and Debugger components. The Internationalization Support portion of the Runtime component and the Times New Roman MT 30 Unicode Font component are always installed on the boot drive. If the Times New Roman MT30 Unicode Font component is installed, the TrueType component is required. The target drive and directory for the other components can be specified by setting the drive and path variables to the desired values. For example, to install the Debugger component in the F:\JAVADEBUG directory: debugger.selection=1 debuggerconfig.selection=1 debugger.dbgdrv=F: debugger.dbgpath=\javadebug If a previous version of Java exists in the specified directory on the target drive, the installation program replaces it. If a previous version of a Java component was installed and you have not selected to reinstall that component, the installation program displays a window that warns you that this component will be downlevel and that lets you choose to upgrade the component. To suppress this confirmation window, along with any others encountered during installation, set the java11.continue variable to UNATTENDED: java11.continue=UNATTENDED ___________________________________________ 2.2.2. Starting the Unattended Installation The CID.CMD file contains a sample CLIFI command for a CID installation. The CLIFI command can also be entered as a single-line command at an OS/2 command prompt as shown below: clifi /a:c /r2:cid.rsp /r:java116.rsp /b:c: /s:d:\tmp /l1:ciderr.log /l2:cidhist.log where: /r Specifies the fully qualified location of the Feature Install response file /b Specifies the boot drive /s Specifies the fully qualified location of the extracted OS/2 Warp Developer's Kit for Java 1.1.6 files /l1 and /l2 Specifies the fully qualified locations of the optional log files. Refer to these files, in addition to the \os2\install\wpinstal.log file on the boot drive, if problems occur during installation. ______________________________________________ 2.2.3. Performing an Unattended Uninstallation To uninstall OS/2 Warp Developer's Kit for Java 1.1.6, enter the following single-line command at an OS/2 command prompt: clifi /a:u /f:"" /o:INV_JAVA11 /set:Selection=ALL _____________________________________________ 2.3. TME-Architected CID Installation Method A JAVA116.ADF file is provided for use with Tivoli Management Environment (TME) architected CID installation products, such as NetFinity Server and the Tivoli TME-10 Software Distribution Agent. See the documentation pertaining to the CID installation product being used for instructions regarding the use of .ADF files. When doing a TME-architected CID installation, you must add the following line to your CID.RSP response file: java11.CID=TME Modifying the CID response file is described in section 2.2.1 of this README. _______________________________________________________ 2.4. NetView DM/2 (NVDM/2) Installation Considerations A NVDM/2 CID installation requires creating a profile and then building and cataloging a change file. The NVDM/2 profile allows you to specify only one response file; however, the OS/2 Warp Developer's Kit for Java 1.1.6 unattended installation requires two response files. In addition, variable and argument handling in NVDM/2 is different than that used in Feature Install, which is used to install OS/2 Warp Developer's Kit for Java 1.1.6. Use one of the following methods to install OS/2 Warp Developer's Kit for Java 1.1.6 using NVDM/2. ___________________________________________ 2.4.1. Put Static Command in NVDM/2 Profile In the NVDM/2 profile, specify all the CLIFI options in the PARMS variable. The parameters must be on a single line and enclosed in double quotation marks: Program=c:\os2\install\clifi.exe Parms="/a:c /r2:cid.rsp /r:java116.rsp /b:c: /s:d:\tmp /l1:ciderr.log /l2:cidhist.log" This method requires you to modify the profile whenever the source directory or log file names are changed. You could replace these values with workstation-specific variable values, as shown below: Program=c:\os2\install\clifi.exe Parms="/a:c /r2:$(ResponseFile) /r:$(SourceDir)\java116.rsp /b:c: /s:$(SourceDir) /l1:$(LogFile1) /l2:$(LogFile2)" ResponseFile=$(WorkstatName).rsp SourceDir=d:\tmp LogFile1=$(WorkstatName).log LogFile2=$(WorkstatName).lg2 This second method requires a separate response file for each workstation and requires WorkstatName to be set appropriately. _________________________________ 2.4.2. Customize JAVA116.RSP File You can directly modify the JAVA116.RSP file with the appropriate information. However, because this file is very large, modifications can be time consuming and error-prone. If you decide to modify the file, see Section 2.5.2 of this README before you begin. ____________________________________________ 2.5. Remote IPL Installation Considerations A remote IPL installation requires creating two response files and setting up the appropriate directories and files on the remote IPL server. Follow these steps for each client to be installed: 1. Place the extracted Java 1.1.6 installation files on the remote IPL server. 2. Run the GENFIRPL command. (See Section 2.5.1 for information.) 3. Run the CLIFI command for one remote IPL client. (See Section 2.5.4 for information.) 4. Modify the client FIT file (See Sections 2.5.3 and 2.5.5) ______________________________ 2.5.1. Creating Response Files After placing the extracted OS/2 Warp Developer's Kit for Java 1.1.6 installation files on the remote IPL server, the GENFIRPL command is used to generate two response files: FILES.RSP for the remote IPL server and JAVA116.RSP for the remote IPL client. The following is a sample GENFIRPL command. The command should be entered on a single line. genfirpl /m:c:\javacode /r:c:\ibmlan\rpl /u:c:\ibmlan\rpluser /f:c:\javacode\java116.rsp /c:client_name /b:x: where: /m Specifies the directory containing the unpacked OS/2 Warp Developer's Kit for Java 1.1.6 installation files on the remote IPL server /r Specifies the RPL directory /u Specifies the RPLUSER directory /f Specifies the fully qualified name of the response file for the remote IPL client /c Specifies the name of the remote IPL client /b Specifies the remote IPL client's boot drive /nf Suppresses Java file transfer. Use this flag when installing additional remote IPL clients, after the first one, to prevent the Java 1.1.6 files from being installed again for each new client. The remote IPL client must not be running when the GENFIRPL command is issued. One GENFIRPL command must be done for each remote IPL client, specifying the appropriate client name and boot drive. _____________________________________ 2.5.2. Modifying the JAVA116.RSP File The JAVA116.RSP file defaults to installing all the components of OS/2 Warp Developer's Kit for Java 1.1.6. You can modify this response file to explicitly set which components you want to install. Be sure to download and extract all the files you need before you start the installation. Be sure to use a text editor that handles lines greater than 255 characters, such as TEDIT, to prevent truncation of the long lines in this file. Because this file is very large, modifications can be time consuming and error-prone. Make a backup copy of JAVA116.RSP before modifying it to prevent loss of data. The component names that can be selected are: Runtime - Java Runtime Unicode - Internationalization Support, part of Java Runtime Environment Toolkit - Toolkit TlktDoc - Toolkit Documentation Samples - Samples Debugger - OS/2 ICAT Debugger for Java Unifont - Times New Roman MT 30 Unicode Font TTengine - Updated TrueType engine, required for the Unicode Font Use the selection variables to select the components to install. The selection variables for the Unifont and TTengine components must be set to the same value. For example, to install only the Runtime and Unicode Font components, set the following variables, which are scattered throughout the JAVA116.RSP file, as shown: runtime.selection=1 runtimeconfig.selection=1 toolkit.selection=0 toolkitconfig.selection=0 tlktdoc.selection=0 tlktdocconfig.selection=0 samples.selection=0 samplesconfig.selection=0 unifont.selection=1 unifontconfig.selection=1 TTengine.selection=1 TTengineconfig.selection=1 Note: There is now a config component associated with each installable component. The config selection variable for each component must always be set to the same value as the selection variable for the component. For example, if you set toolkit.selection=0, you must also set toolkitconfig.selection=0. _________________________________________ 2.5.3. Updating Files for Feature Install The client_name.FIT file for each remote IPL client must be modified to include the following, which must be entered on a single line: x:\os2\install\install.inv \\server_name\WRKFILES\client_name\os2\install\install.inv Substitute the name of the remote IPL server and remote IPL client for server_name and client_name. ___________________________________________ 2.5.4. Starting the Remote IPL Installation Remote IPL installations are handled by CLIFI, the Feature Install installation program, and can take 15 to 20 minutes or more. After logging on to the remote IPL server as an administrator, run the CLIFI command, using the response file created for the remote IPL server, FILES.RSP: clifi /a:i /r:c:\javacode\files.rsp where /r specifies the fully qualified name of the remote IPL server's response file. It is necessary to reboot the remote IPL Server after running clifi if file transfer has not been suppressed. Run the CLIFI command on each remote IPL client after you run the GENFIRPL command for that client. clifi /a:i /r:z:\java116.rsp where /r specifies the fully qualified name of the remote IPL client's response file, as specified on the GENFICMD command. ________________________________________________________ 2.5.5. Running the Java Samples from a Remote IPL Client The remote IPL server administrator must add the following lines to the RPL\FITS\client_name.FIT file to give the remote IPL client the ability to run the samples provided in the Samples component: x:\JAVA11\WEBLOGS \\server_name\WRKFILES\client_name\JAVA11\WEBLOGS x:\JAVA11\HOTJAVA \\server_name\WRKFILES\client_name\JAVA11\HOTJAVA Substitute the names of the remote IPL server and remote IPL client for server_name and client_name. The remote IPL clients can compile the sample code if the samples are placed in a directory to which the remote IPL client has write access. _______________________________________________________________________ 2.5.6. Upgrading Java 1.1.4 to Java 1.1.6 in the Remote IPL Environment To upgrade Java 1.1.4 to Java 1.1.6 in the remote IPL environment: 1. Place the extracted Java 1.1.6 installation files on the remote IPL server. 2. Run the GENFIRPL command. (See Section 2.5.1 for information.) 3. Run the CLIFI command for one remote IPL client. (See Section 2.5.4 for information. This process updates the Java files on the remote IPL server. Because all remote IPL clients access the same files on the server, the upgrade is done for all clients. The client configuration information is present from the Java 1.1.4 installation. ______________________________ 2.5.7. Remote IPL Restrictions You cannot uninstall OS/2 Warp Developer's Kit for Java 1.1.6 in the remote IPL environment. ____________________________________________________________ 2.6. Installing OS/2 Warp Developer's Kit for Java 1.1.6 on WorkSpace On-Demand WorkSpace On-Demand is a client-server system that uses network computers (clients) that are designed to be remotely loaded from a network server. The WorkSpace On-Demand client runs Java applications, Netscape Navigator, and the Personal Communications Entry Level host access application, as well as other applications; it also supports native execution of DOS, Windows 3.1, and OS/2 applications. The WorkSpace On-Demand server runs on an OS/2 Warp Server and provides enhanced server support to manage the clients. The WorkSpace On-Demand product includes Java 1.1.1 for OS/2 Warp. You can install OS/2 Warp Developer's Kit for Java 1.1.6 on WorkSpace On-Demand servers and clients to upgrade from Java 1.1.1. __________________________________________________________________ 2.6.1. Installing OS/2 Warp Developer's Kit for Java 1.1.6 for Use on a WorkSpace On-Demand Server To install Java 1.1.6 on a WorkSpace On-Demand server, use the GUI. See Section 2.1 of this README for instructions for using the GUI to install. During installation on a WorkSpace On-Demand server, a warning is displayed explaining that you are not updating Java support for the client. When you select "Yes", installation proceeds as for other GUI installations. ________________________________________________________________ 2.6.2. Installing OS/2 Warp Developer's Kit for Java 1.1.6 for a WorkSpace On-Demand Client Installation of Java 1.1.6 on a WorkSpace On-Demand Client is done as an unattended (CID) installation. You can use the instructions in Section 2.2 of this README and use the CID.CMD and WSOD.RSP files that are included in the Java 1.1.6 installation package. _______________________________________________________________ 2.6.2.1. Requirements for Installation on a WorkSpace On-Demand Client Before you can install Java 1.1.6 for a WorkSpace On-Demand client, Java 1.1.1 must already be installed. If the Times New Roman MT 30 Unicode Font (the Unifont component) is selected for installation, it must also have been previously installed with WorkSpace On-Demand. If this support is not present, the installation is completed without transferring files. In this case, the wpinstal.log shows that installation completed successfully but it does not show that any files were transferred. _________________________________________________ 2.6.2.2. Modifying the CID.CMD and WSOD.RSP Files Before starting the installation, modify the CID.CMD and WSOD.RSP files as follows: 1. In the CID.CMD file, change /r2:cid.rsp to /r2:wsod.rsp. 2. As described in Section 2.2.2: - Replace /s:d:\javainst in the CID.CMD file with the drive and directory where you unzipped the install package. - Be sure that /b:c in the CID.CMD file points to the boot drive. 3. Verify that the selections in the WSOD.RSP files are appropriate for what you want to install. By default the Java Runtime Environment and Unicode Font are selected; all other components are deselected. Be sure to download and extract all the files you need. ___________________________________________________________ 2.6.2.3. Installing Additional Java 1.1.6 Components on the Workspace On-Demand Client If you want to install components other than the Java Runtime Environment and Unicode font for the WorkSpace On-Demand client, you can select these components in the WSOD.RSP file. If you install the ICAT Debugger, a WorkSpace On-Demand administrator must make the following additions to the CONFIG.SYS files for the clients: - Add Z:\java11\icatjava\dll; to the LIBPATH statement. - Add Z:\java11\icatjava\bin; to the SET PATH statement. - Add Z:\java11\icatjava\help; to the SET DPATH and SET HELP statements. - Add Z:\java11\icatjava\daemon\javaprob.zip; to the SET CLASSPATH statement. - Add RUN=Z:\mptn\bin\ifconfig.exe lo 127.0.0.1 up Substitute the drive and directory where the ICAT debugger is installed for Z:\java11. ____________________________________________ 2.6.3. Uninstalling from WorkSpace On-Demand Support for uninstalling Java 1.1.6 requires access to an inventory object in the Installed Features directory (\os2\install\installed features). If you install Java 1.1.6 both for the WorkSpace On-Demand client and the WorkSpace On-Demand server, the Java 1.1.6 inventory object is damaged or replaced. To remove Java 1.1.6 from the client space, reinstall the WorkSpace On-Demand version of Java 1.1.1. This installation will replace Java 1.1.6. To remove Java 1.1.6 from the server, delete the \java11 directory structure. You can delete the directory structure from the Drives folder in the OS/2 System folder. In addition, if you installed the Unicode Font, delete the file \os2\dll\tnrmt30.ttf, which is on the boot drive. ________________________________________________________ 3. Uninstalling OS/2 Warp Developer's Kit for Java 1.1.6 To uninstall OS/2 Warp Developer's Kit for Java 1.1.6, use the Remove Java 1.1.6 for OS/2 object or the UNINSTAL program. These methods are described in the sections that follow. These sections also describe how to optionally restore some OS/2 base operating system files to their previous versions. ____________________ 3.1. Desktop Method To uninstall using the Remove Java 1.1.6 object, follow these steps: 1. Open the OS/2 System folder. 2. Open the System Setup folder. 3. If you are uninstalling from an OS/2 Warp 4 system only, open the Install/Remove folder. 4. Open the Uninstall Features folder. 5. Select the Remove Java 1.1.6 for OS/2 object to start the uninstall program. 6. (Optional) Follow the instructions in section 3.3 to restore base OS/2 files if they were saved before installing OS/2 Warp Developer's Kit for Java 1.1.6. ________________________________ 3.2. OS/2 Command Prompt Method To start uninstalling, make sure that you are either in the directory where the OS/2 Warp Developer's Kit for Java 1.1.6 files were extracted or in the \JAVA11\UNINSTAL directory. At an OS/2 command prompt, enter: uninstal The uninstall program leads you through the uninstallation process. Only files and directories created by the installation process are removed. For instance, the HOTJAVA directory created by running the Applet Viewer is not removed during uninstallation. You can optionally choose to restore base OS/2 files that were saved before installing OS/2 Warp Developer's Kit for Java 1.1.6 by following the instructions in the next section. _______________________________ 3.3. Restoring Base OS/2 Files In most cases, the base OS/2 files replaced during the installation of OS/2 Warp Developer's Kit for Java 1.1.6 can be used after you uninstall OS/2 Warp Developer's Kit for Java 1.1.6. If you made copies of the original files, as described in section 1.5 of this README, you can optionally choose to restore them. Some of the files you backed up are locked during normal system operation and cannot be overwritten with the backup copy while the system is running. To replace these files, follow these steps: 1. Restart the computer. 2. When the white block and the name OS/2 are displayed in the top left hand-corner of the display, press Alt+F1. 3. Select the option to boot to an OS/2 command line. 4. Restore the files with the ones you saved before installing OS/2 Warp Developer's Kit for Java 1.1.6. 5. At an OS/2 command prompt, type: exit and press Enter. The system now restarts. ___________________________________________________________ 3.4. State of CONFIG.SYS File After Uninstalling Java 1.1.6 If you installed Java 1.1.6 over Java 1.1.x and you later uninstall Java 1.1.6, the CONFIG.SYS file is returned to the Java 1.1.x level. _________________________________________________________________________ 3.5. Entries Left in CONFIG.SYS File after Uninstalling Toolkit Component If you install the Toolkit component of Java 1.1.6 and later uninstall the component, the SET LIB= and SET INCLUDE= statements in the CONFIG.SYS might still contain references to the directory where the Toolkit component was installed. _______________________________ 3.6. Unattended Uninstallation For information about performing an unattended uninstallation, see Section 2.2.3 of this README. _________________________________________ 3.7. Uninstalling on WorkSpace On-Demand For information about uninstalling on WorkSpace On-Demand, see Section 2.6.3 of this README. ________________________________________________________________________ 4. After You Install The following sections provide additional information you might need after you install OS/2 Warp Developer's Kit for Java 1.1.6. _______________________________________ 4.1. Additional Sources of Information The objects in the following list are displayed in the Java 1.1.6 for OS/2 folder only if you are running OS/2 Warp 4. If you are running OS/2 Warp Server or OS/2 Warp 3, you can access the associated documents at the locations shown. (x: is the partition where you installed Java.) IBM Centre for Java Technology http://ncc.hursley.ibm.com/javainfo/hurindex.html Running Java x:\JAVA11\runtime.htm Configure Applet Viewer x:\JAVA11\cnfgappl.htm Java Documentation http://www.javasoft.com/doc.html Java Developer's Kit for OS/2 x:\JAVA11\index.html Java Toolkit x:\JAVA11\toolkit.html Java API x:\JAVA11\docs\api\API_users_guide.html ICAT Debugger for OS/2 Java x:\JAVA11\ICATJAVA\help\icatjava.htm If you installed the Toolkit, Toolkit Documentation, or ICAT Debugger for OS/2 Java components in different directories than the Runtime component, specify the appropriate directory for the last four objects listed above. The links to the Runtime documentation, the ICAT Debugger for OS/2 Java, and README in the Toolkit documentation do not work if the components are in different places. ______________________________________ 4.2. Installing Additional Components After the initial installation of OS/2 Warp Developer's Kit for Java 1.1.6, you can install additional components by re-running the installation procedure. This requires that you keep all of the extracted files on your system or that you keep the original ZIP files and extract the files again when needed. _______________________________________________________________________ 4.3. Starting a Java Application that Calls a Non-Presentation Manager Program If you start a Java application that calls a non-Presentation Manager program, use the -norestart option. For example, if Java application JavaApp calls a non-Presentation Manager program, start it by typing java -norestart JavaApp at the OS/2 command prompt. Errors occur if you do not use the -norestart option. _______________________________________________ 4.4. Disabling the Just-In-Time (JIT) Compiler A just-in-time (JIT) compiler is provided with OS/2 Warp Developer's Kit for Java 1.1.6. This compiler generates machine code for frequently used byte-code sequences in a Java application or applet on-the-fly during execution. The JIT is enabled by default. You can disable the JIT to aid in the isolation of a problem with a Java application, an applet, or the compiler itself. See the RUNTIME.HTM file in the x:\JAVA11 directory for details. (x is the drive on which Java is installed.) When the JIT compiler is enabled, an uncaught exception generates a trace back without source line numbers. You must disable the JIT and run the failing application again to obtain a trace back with line numbers. __________________________________________ 4.5. Native Methods Need to be Recompiled Java methods implemented using version 1.0x of Java in a native language, such as C or C++, need to be recompiled for OS/2 Warp Developer's Kit for Java 1.1.6. See the TOOLKIT.HTML file for details. This file is in the directory where you installed the Java Toolkit component. ___________________________________________________ 4.6. LIBPATH Changes That Could Affect Your System When the installation program determines that the OS/2 base DLL modules that need to be replaced exist in a directory other than x:\OS2\DLL, the position of x:\OS2\DLL is changed in the LIBPATH to ensure that the correct version of the modules are loaded. The IBM Developer's Toolkit for OS/2 Warp is one product that includes OS/2 base DLL modules in a different directory. This change does not affect the Toolkit, but could affect other products that include OS/2 base DLL modules. ______________________ 4.7. Timer Resolution The environment variable JAVA_CLOCK_RESOLUTION allows you to specify the timer resolution you require from the currentTimeMillis method in the java.lang.System class. The resolution is specified in milliseconds. For example: SET JAVA_CLOCK_RESOLUTION = 1 sets the minimum timer resolution to 1 millisecond (the highest resolution) for Java applications that use currentTimeMillis. The timer resolutions available are dependent on those provided by the OS/2 system. The Java system rounds down to the nearest available resolution. 1 millisecond is always available and is the highest resolution available. The default for JAVA_CLOCK_RESOLUTION is 10 milliseconds, and this is generally rounded to 1 millisecond accuracy. If you need to ensure that the best Java performance is obtained when using currentTimeMillis, set JAVA_CLOCK_RESOLUTION = 32. This can be important when running Java benchmarks. ______________________________________________________________________ 4.8. Applying OS/2 Service after Installing OS/2 Warp Developer's Kit for Java 1.1.6 OS/2 Warp Developer's Kit for Java 1.1.6 replaces base operating system modules as part of installation. When you apply service to your OS/2 system after installing OS/2 Warp Developer's Kit for Java 1.1.6, you are normally prompted if you attempt to replace a module that is newer than the one on the FixPak. However, if you install service by booting from the FixPak diskettes, you are not prompted when this condition exists, which could result in one or more modules being regressed. Either do not apply service by booting from the diskettes, or back up the base OS/2 modules before installing service and replace them after applying service. A complete list of new and changed base modules is provided in section 5 of this README. ____________________________________________________________________ 4.9. Installing a FixPak on OS/2 Warp Server or OS/2 Warp 3 Systems after Java 1.1.6 If you install FixPak 30 or greater (or DBCS equivalent) on an OS/2 Warp Server or OS/2 Warp 3 system after you have installed OS/2 Warp Developer's Kit for Java 1.1.6, and you want to use the Unicode Font support, you must reinstall the Runtime and Times New Roman MT 30 Unicode Font components. _______________________________________________________________________ 4.10. Using 16-Color Mode with OS/2 Warp Developer's Kit for Java 1.1.6 The Java 1.1.6 specification requires 256-color mode (or greater). OS/2 Warp Developer's Kit for Java 1.1.6 does not support Java applications and applets using the Abstract Window Toolkit (AWT) in 16-color mode. ___________________________________ 4.11. JDBC-ODBC Bridge Not Provided OS/2 Warp Developer's Kit for Java 1.1.6 provides JDBC (Java Database Connectivity), a database access interface that provides access to a wide range of relational databases. However, not all relational databases provide a JDBC driver. To access databases that support the Open Database Connectivity (ODBC) standard, a JDBC-ODBC Bridge is needed. The JDBC-ODBC Bridge allows ODBC drivers to be used as JDBC drivers by using native code to interface with ODBC. OS/2 Warp Developer's Kit for Java 1.1.6 does not provide a JDBC-ODBC bridge. _______________________________________________ 4.12. AWT TextField and TextArea Considerations The AWT TextField and TextArea controls do not support characters outside of the current code page. Users running on US English systems can switch to code page 850 (the multilingual code page, which supports the Western European languages) to see additional language characters in these controls. _________________________________________________ 4.13. Controlling Arabic Number Character Display Users in some countries could unexpectedly see Arabic number characters appear. Some country-specific versions of OS/2 map the characters x'00B0' through x'00B9' to the Arabic numbers 0 through 9. To see the desired characters, change the Bidirectional Attributes in CONFIG.SYS or use the Language page in the Properties Notebook (Settings Notebook in OS/2 Warp Server or OS/2 Warp 3) of the object to obtain the desired effect. ___________________________________________________ 4.14. Modifying Font Properties Files Not Supported Modifying the font properties files provided with OS/2 Warp Developer's Kit for Java 1.1.6 is not supported. _____________________________ 4.15. Printing Considerations Java provides no mechanism to communicate with the printer driver in order to set or retrieve job properties. Printing from a Java application or applet results in a printer properties dialog box being displayed. OS/2 Warp Developer's Kit for Java 1.1.6 provides an environment variable called JAVA_NOPRINTDLG that suppresses the dialog box and prints the file using the default properties. To suppress the dialog box and use the default print properties: SET JAVA_NOPRINTDLG=1 ______________________________________________________ 4.16. Backslash and Tilde Characters in DBCS Countries Certain DBCS code pages (for example, 932, 942, 943, 949) do not have a backslash or tilde character at the same code point as all other ASCII code pages. In most ASCII code pages, code point 0x5c is a backslash and code point 0x7e is a tilde. In code pages 932, 942, and 943, code point 0x5c is a Japanese Yen mark and code point 0x7e is an overline. In code page 949, code point 0x5c is a Korean Won sign. The Java compiler, javac, first converts the Java source program from the local code page to Unicode. It then processes the character escape sequences, such as \n, by reading the backslash character, then the 'n' character, and then combining them as a character escape to generate a Unicode newline, U+000A, before compiling the program. A problem exists because the backslash character, which is character 0x5C in code page 850, is not in the same position in certain DBCS code pages. For example, in code page 943, character 0x5C is a Yen character. If the javac compiler converted code point 0x5c in the local code page (a Yen mark) in the Java source program to a Unicode Yen mark (U+00A5), then no backslash characters would be present, so no character escape sequence processing would be performed. Furthermore, in code pages 932, 943, and 949, there is no backslash anywhere in the local code page, so there is no way for a programmer to generate a Unicode backslash (for use in generating other Unicode characters using Unicode escape sequences) after code page conversion in the javac compiler. To allow programmers to write programs containing a backslash, the Java virtual machine uses modified code page conversion tables for code pages 932, 943, and 949. These modified tables pass through characters 0x00 to 0x7F in the local code page to U+0000 to U+007F in Unicode. This means that a programmer can use a Yen mark (0x5c) in code page 932 and 943 and a Won sign (0x5c) in code page 949 to represent a backslash character (U+005C) in Unicode. An overline (0x7e) in code pages 932 and 943 can be used to represent a tilde (U+007E) in Unicode. These modified codepage conversion tables are also used as the default for the Java Virtual Machine when running in OS/2 code pages 932, 943, and 949. These are used for PrintStream, PrintWriter, OutputWriter and InputReader classes when no explicit character encoding is specified. Although using 0x5C in the local code page may be printed as a Yen mark in the local code page, if an application programmer really wants a Yen mark, then a Unicode escape should be used to generate a Unicode character U+00A5. This is needed to make the application portable to other code pages, and also to cause AWT to display the correct character glyph. Similar considerations apply if the programmer wants a real overline: Unicode character U+203E should be used within the Java program. Code page 942 Code page 942 has both tilde and backslashes present, though at different code points from other code pages. Because this code page does have backslashes and tildes present, even though they are in different positions from other ASCII code pages, the modified code page converters are not used by default. Programs written in this code page can be written using real backslashes and tilde symbols in the local code page. If programs are written in another ASCII code page where backslash is code point 0x5C and they need to be compiled, then in most cases, the proper behavior can be achieved by using one of the following methods: - Replace the 0x5c character in the Java source program with the backslash character in the local code page (code point 0xfe). - When compiling the Java application or applet, indicate that the file is written in a code page different from the local code page. For example, if the source code was written in code page 850, use the following command to compile it: javac -encoding 850 myprogram.java If the file is written with DBCS characters in code page 942, using 0x5C to represent the backslash, then the -encoding option of javac can be used to force the use of character encoding Cp942c', which passes through characters 0x00 to 0x7F in the local code page to U+0000 to U+007F in Unicode. For example: javac -encoding Cp942c myprogram.java If the source program is written in code page 942 using a real backslash (code point 0xfe) and must be compiled on another system, then use the native2ascii program to convert the Java source program from the local code page to a basic ASCII code page. For example: native2ascii myprogram.java d:\mydest\myprogram.java To convert from a specific code page to a basic ASCII code page: native2ascii -encoding 942 myprogram.java d:\mydest\myprogram.java The file separator character in most ASCII code pages on OS/2 is a backslash. The file separator character is accessible in a Java program using the system property 'file.separator' or the static constant 'java.io.File.separator'. In code pages 932 and 943, the local file separator character is still code point 0x5C, but this is displayed at the command prompt as a Yen mark. Similarly, in code page 949, the separator character is displayed as a Won sign. The default character converter for these code pages converts the file.separator character to a backslash in Unicode, so a Java application sees the file separator as a Unicode backslash (U+005C). In code page 942, the local file separator is also a Yen mark, but this is converted by the Java character converter to a Yen mark in Unicode, so the Java application sees the file separator character as a Unicode Yen mark (U+00A5). Because well-written Java applications always use the file.separator system property so that they can work on UNIX systems where the file separator is a forward slash, this should not be a problem. Application programmers should be sure not to embed path separators in their programs. For example, do not use: FileInputStream x = new FileInputStream("mydir\myfile.ext"); Instead, use: FileInputStream x = new FileInputStream("mydir" + File.separator+ "myfile.ext"); ______________________________________________________________________ 4.17. Using Java 1.0.2 for OS/2 After Installing OS/2 Warp Developer's Kit for Java 1.1.6 The use of Java 1.0.2 for OS/2 is not supported from an OS/2 Command Prompt or the Desktop after you have installed OS/2 Warp Developer's Kit for Java 1.1.6. You can attempt to run Java 1.0.2 for OS/2 from an OS/2 Command Prompt by setting the LIBPATH, PATH, and CLASSPATH in the session as follows: SET BEGINLIBPATH=x:\JAVAOS2\DLL; SET PATH=x:\JAVAOS2\BIN;%PATH% SET CLASSPATH=x:\JAVAOS2\LIB\JEMPCL10.ZIP;.\. where x: is the drive that contains Java 1.0.2 for OS/2. This method of running Java 1.0.2 for OS/2 has not been officially tested and is not supported. ________________________________________ 4.18. Problems with Time in Java Applets If you have problems with time in your Java applets, you might need to set or change the timezone (TZ) variable. To set the TZ variable, do one of the following: - Go to the General page in the TCP/IP Configuration notebook. Set the timezone field, using the online help provided. - Edit the CONFIG.SYS file and add or change the SET TZ= statement. __________________________________________________ 4.19. Korean OS/2 Users Need PTF for Updated Fonts If you want to install OS/2 Warp Developer's Kit for Java 1.1.6 on a Korean OS/2 system, you must apply PTF PK0817 to your system first. To obtain the PTF, contact your local IBM OS/2 support representative. Without this PTF applied, Korean characters might not display correctly on your OS/2 system after installing OS/2 Warp Developer's Kit for Java 1.1.6. _________________________________________________________ 4.20. TrueType Fonts Must Be Installed on Chinese Systems On Simplified or Traditional Chinese systems, ensure that all available OS/2 TrueType fonts have been installed. To install these fonts, do the following: 1. Start the Selective Install program by typing C:\OS2\INSTALL\INSTALL at an OS/2 command prompt, where C: is the boot drive. A panel titled "System Configuration" is displayed. 2. Continue to the OS/2 Setup and Installation panel by clicking on the Next buttons (for Warp 4.0) or the OK button (for Warp Server 4.0 or OS/2 Warp 3). 3. On the OS/2 Setup and Installation panel, click on the TrueType Fonts check box. 4. Select the More button to the right of this check box. 5. Make sure all font check boxes are selected. Click OK. 6. Insert the operating system CD (OS/2 Warp Server 4.0, OS/2 Warp 4.0, OS/2 Warp 3) into the CD drive. 7. Click OK on the Source Directory panel. The appropriate fonts are installed. Restart your system when the font installation is completed. ____________________________________________________________ 4.21. Conversion between ShiftJIS and Unicode on OS/2 Warp 4 Japanese version In the Japanese environment, the following conversion tables for ShiftJIS code (PC code) and Unicode are available: SJIS Cp943c Cp943 = IBM-943 Cp942 = IBM-942 Cp942c The system default conversion tables are: - Cp943c for code pages 943 and 932 - Cp942 for code page 942 To use the Cp942 table, set the table name explicitly in a method or as a parameter. These tables do the following conversions: For SBCS characters: PC code Unicode ------------------------------------------------------------------- SJIS 0x00-0x7F U0000-U007F Cp942c Cp943c Cp942 0x00-0x5B U0000-U005B Cp943 Yen sign 0x5c U00A5 Yen Sign 0x5D-0x7D U005D-U007D Overline 0x7E U203E Overline 0x7F U007F Cent sign 0x80 U00A2 Cent sign Pound sign 0xA0 U00A3 Pound sterling sign Not sign 0xFD U00AC Not sign Backslash 0xFE U005C Backslash Tilde 0xFF U007E Tilde For example, in the Cp943c table, the PC code for the range range 0x00 - 0x7F is converted to Unicode for the range U0000 - U007F straight. In the Cp942 table, the PC code Yen sign (0x5c) is converted to the Unicode Yen sign (U00A5). For DBCS characters: In the Cp943, Cp943c and SJIS table, the PC code is regarded as the new JIS order. In the Cp942 and Cp942c table, the PC code is regarded as the old JIS order. For User-Defined Characters and IBM Extended Characters: In the Cp943 and Cp943c tables, these PC code characters are converted to Unicode. In the SJIS table, these PC code characters are NOT converted to Unicode. In the Cp942 and Cp942c tables, these PC code characters are converted to Unicode. _____________________________________________________________ 4.22. Installing Japanese FixPak 2 (FX00002) over OS/2 Warp 4 Japanese version (without VoiceType) and Java 1.1.6 Before you apply the Japanese FixPak 2 after installing OS/2 Warp Developer's Kit for Java 1.1.6 on OS/2 Warp 4 Japanese version (without VoiceType), back up the following files to another directory: \os2\dll\INSTALL.DLL \os2\dll\UCONV.DLL \os2\dll\TRUETYPE.DLL After applying the FixPak, restore them. To restore them: 1. Restart the system. 2. When the white box with "OS/2" next to it is displayed in the upper-left corner, press Alt+F1. 3. From the menu selection, press F2. 4. At an OS/2 command prompt, copy these files back into the \os2\dll directory. 5. Type: exit The system restarts. Note: OS/2 Warp 4 Japanese version (with VoiceType) includes FixPak 2(FX00002). ________________________________________________________________________ 5. List of OS/2 Base Modules Changed or Added by OS/2 Warp Developer's Kit for Java 1.1.6 When you install OS/2 Warp Developer's Kit for Java 1.1.6 on your system, the following OS/2 base files are updated, or they are added if they do not already exist: \os2\dll\libaux.dll \os2\dll\libcm.dll \os2\dll\libcn.dll \os2\dll\libcs.dll \os2\dll\libtk.dll \os2\dll\libuni.dll \os2\dll\locale.dll \os2\dll\uconv.dll \language\codepage\ibm437 \language\codepage\ibm813 \language\codepage\ibm819 \language\codepage\ibm850 \language\codepage\ibm852 \language\codepage\ibm855 \language\codepage\ibm857 \language\codepage\ibm860 \language\codepage\ibm861 \language\codepage\ibm862 \language\codepage\ibm863 \language\codepage\ibm864 \language\codepage\ibm865 \language\codepage\ibm866 \language\codepage\ibm869 \language\codepage\ibm874 \language\codepage\ibm878 \language\codepage\ibm912 \language\codepage\ibm913 \language\codepage\ibm914 \language\codepage\ibm915 \language\codepage\ibm916 \language\codepage\ibm920 \language\codepage\ibm921 \language\codepage\ibm922 \language\codepage\ibm942 \language\codepage\ibm943 \language\codepage\ibm949 \language\codepage\ibm950 \language\codepage\ibm1004 \language\codepage\ibm1089 \language\codepage\ibm1200 \language\codepage\ibm1207 \language\codepage\ibm1208 \language\codepage\ibm1250 \language\codepage\ibm1251 \language\codepage\ibm1252 \language\codepage\ibm1253 \language\codepage\ibm1254 \language\codepage\ibm1255 \language\codepage\ibm1256 \language\codepage\ibm1257 \language\codepage\ibm1275 \language\codepage\ibm1280 \language\codepage\ibm1281 \language\codepage\ibm1282 \language\codepage\ibm1283 \language\codepage\ibm1381 \language\codepage\ibm1386 \language\codepage\os2ugl \language\codepage\ucstbl.lst The following file is replaced on OS/2 Warp 4 systems and on OS/2 Warp Server or OS/2 Warp 3 systems at a FixPak 30 service level or higher: \os2\dll\truetype.dll The following file contains Monotype Corporation's Times New Roman MT 30 TrueType Unicode Font and is installed on OS/2 Warp 4 systems and on OS/2 Warp Server or OS/2 Warp 3 systems at a FixPak 30 or higher level. If you have previously installed a font with the same file name, this file replaces it: \os2\dll\tnrmt30.ttf ________________________________________________________________________ 6. TRADEMARKS The following terms are trademarks of the IBM Corporation in the United States or other countries or both: IBM OS/2 Java and HotJava are trademarks of Sun Microsystems, Inc. in the U.S. and other countries. The Java technology is owned and exclusively licensed by Sun Microsystems, Inc. Netscape and Netscape Navigator are trademarks of Netscape Communications Corporation. PartitionMagic is a trademark of PowerQuest Corporation. Intel and Pentium are registered trademarks of Intel Corporation in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS. (C) Copyright IBM Corporation 1998, All rights reserved. ________________________________________________________________________ END-OF-README-FILE ________________________________________________________________________