  ________________________________________________________________________

  IBM OS/2 WARP DEVELOPER KIT, JAVA(TM) TECHNOLOGY EDITION, VERSION 1.1.8  
  INSTALLATION README
  ________________________________________________________________________

  IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition, Version 1.1.8 
  (Developer Kit) is based on Sun Microsystems' Java 1.1.8 maintenance 
  level. 
  
  The Developer Kit provides the Sun Microsystems, Inc. Java environment 
  for the following products:

    OS/2 Warp 4 with FixPak 5 or higher or DBCS equivalent
    OS/2 Warp Server with FixPak 32 or higher or 
      DBCS equivalent
    OS/2 Warp Server Advanced with FixPak 32 or higher or 
      DBCS equivalent
    OS/2 Warp Server Advanced SMP Feature with FixPak 32 
      or higher or DBCS equivalent
    OS/2 Warp Server for e-business    
    WorkSpace On-Demand clients and servers
    OS/2 Warp 3 with FixPak 32 or higher or DBCS equivalent
    OS/2 Warp Connect with FixPak 32 or higher or DBCS equivalent
    
    Note:  For information on the Double Byte Character Set (DBCS)
           FixPak equivalents, see the "FixPaks" section.

  References in this README are as follows: 
    o  OS/2 Warp 4 refers to the OS/2 Warp 4 client operating system and 
       the WorkSpace On-Demand client. 
    o  OS/2 Warp Server refers to all of the OS/2 Warp Server operating 
       systems and the WorkSpace On-Demand server. 
    o  OS/2 Warp 3 refers to OS/2 Warp Version 3 and OS/2 Warp Connect. 
    o  Java 1.1.x refers to Java 1.1.1 for OS/2, Java 1.1.4 for OS/2 
       Warp, IBM OS/2 Warp Developer Kit, Java(TM) Edition, 1.1.6, IBM 
       OS/2 Warp Developer Kit, Java(TM) Edition, 1.1.7.

  This README guides you through installation of the Developer Kit 
  and provides information about limitations and solutions for 
  them. References to objects specific to this product are referred to 
  as, Java 1.1.8  objects.

  Depending on the executable file you are using, the IBM build 
  and version number can be obtained by typing the following at 
  a command line:
  
    o  java -fullversion  
       (If you are using the java.exe executable file.)
    o  jre -d
       (If you are using the jre.exe executable file.)
  ________________________________________________________________________
  CONTENTS

     1.0  BEFORE YOU INSTALL
     1.1  HPFS or JFS and FAT Partition Considerations
     1.1.1  Use of a Single FAT Partition
     1.2  Making a Copy of Your Current CONFIG.SYS File
     1.3  Disk Space Requirements
     1.4  Hardware Requirements
     1.5  FixPaks   
     1.6  Installing FixPaks after the Developer Kit
     1.7  Replacing Previous Versions of Java 1.1.x
     1.8  Backing Up Base OS/2 Files
     1.9  Netscape Navigator 2.02 Refresh and Java 1.1.x
     1.10 Running Netscape Navigator 4.04 While Installing the 
          Developer Kit 
     1.11  Netscape Communicator 4.04 and the JIT Compiler
     1.12 Java Integration Layer for Netscape Communicator 4.04   

     2.0  INSTALLING THE DEVELOPER KIT
     2.1  Installing the Developer Kit Through the GUI
     2.1.1  Desktop Method
     2.1.2  OS/2 Command Prompt Method
     2.1.3  Components Not Selectable During Installation
     2.1.4  Recovering from a Failed Installation
     2.1.4.1  Cannot Remove the Install Object 
     2.2  Unattended (CID) Installation Method
     2.2.1  Modifying the CID Response File
     2.2.1.1  Configuration Components
     2.2.1.2  Installation Drives of the Components     
     2.2.2  Starting the Unattended Installation
     2.3  TME-Architected CID Installation Method
     2.4  Installing the Developer Kit on WorkSpace 
          On-Demand     
     2.4.1  Installing the Developer Kit on a WorkSpace 
            On-Demand Server 
     2.4.2  Installing the Developer Kit on a WorkSpace 
            On-Demand Client 
     2.4.2.1  Requirements for Installation on a WorkSpace 
              On-Demand Client
     2.4.2.2  Modifying the CID.CMD and WSOD.RSP Files
     2.4.2.3  Multiple Releases of Workspace On-Demand on the 
              Same Server     
     2.4.2.4  Installing Additional Developer Kit Components on the 
              Workspace On-Demand Client
     2.4.2.5  The JIT Compiler and Workspace On-Demand
     2.5  NetView DM/2 (NVDM/2) Installation Considerations 
     2.5.1  Put Static Command in NVDM/2 Profile
     2.6  Remote IPL Installation 
     2.6.1  Creating Response Files
     2.6.2  Modifying the JAVA118.RSP File
     2.6.3  Updating Files for Feature Install
     2.6.4  Starting the Remote IPL Installation
     2.6.5  Running the Java Samples from a Remote IPL Client
     2.6.5.1  Issuing a Trust on WorkSpace On-Demand
     2.6.6  Upgrading 1.1.x to the Developer Kit in the 
            Remote IPL Environment
     
     3.0  AFTER YOU INSTALL
     3.1  Additional Sources of Information
     3.2  Installing Additional Components
     3.3  JDBC-ODBC Bridge Not Provided
     3.4  AWT TextField and TextArea Considerations
     3.5  Modifying Font Properties Files Not Supported
     3.6  Time Problems in Java Applets 
     3.7  LIBPATH Changes That Could Affect Your System
     3.8  Verification Exception
     3.9  Using the OS/2 High Memory Support to Increase
          the Java Heap Size
     3.9.1  Enabling OS/2 HMS
     3.9.2  Enabling Java Heap Size to Use OS/2 HMS
     3.9.3  Limitations When Using OS/2 HMS        
     3.10  Enhanced BigDecimal Class
 
     4.0  DOUBLE-BYTE CHARACTER SET (DBCS) CONSIDERATIONS
     4.1  Installation Panel Text Missing or Too Long in DBCS Countries
     4.2  Korean OS/2 Users Need PTF for Updated Fonts
     4.3  TrueType Fonts Must Be Installed on Chinese Systems
     4.4  Controlling Arabic Number Character Display 
     4.5  Installing Japanese FixPak 2 (FX00002) after OS/2 Warp 4
          Japanese version (without VoiceType) and the Developer Kit
     4.6  Japanese Environment Settings on OS/2 Warp 4 Japanese Version
     4.7  Required Fonts on OS/2 Warp Japanese Version
     4.8  Modifying the CONFIG.SYS File for DBCS Languages on 
          Warp 3 Connect

     5.0  LIST OF OS/2 BASE MODULES CHANGED OR ADDED BY THE DEVELOPER KIT
     
     6.0  UNINSTALLING THE DEVELOPER KIT
     6.1  Desktop Method
     6.2  OS/2 Command Prompt Method
     6.3  Uninstalling from WorkSpace On-Demand     
     6.4  Performing an Unattended Uninstallation
     6.5  Restoring Base OS/2 Files

     7.0  NOTICES

     8.0  TRADEMARKS
  

  1.0  BEFORE YOU INSTALL
  ________________________________________________________________________

  You can download the following extensions as part of the Developer Kit.
  
    o  Swing Runtime, Supported by IBM (Swing Runtime)
    o  Swing Toolkit, Supported by IBM (Swing Toolkit) 
    o  RMI-IIOP Toolkit, Supported by IBM (RMI-IIOP Toolkit)

  The RMI-IIOP Runtime, Supported by IBM (RMI-IIOP Runtime) is integrated 
  in the Developer Kit's Runtime packages.  
 
  A Runtime package must be installed to use any component other than 
  the Toolkit documentation. You cannot install the Toolkit, Samples, 
  Swing Runtime, Swing Toolkit, RMI-IIOP Toolkit, or Interactive Code
  Analysis Tool (ICAT) Debugger unless you are also installing the 
  Runtime component or have previously installed the Runtime 
  component and rebooted the system.

    1.1  HPFS or JFS and FAT Partition Considerations
    ______________________________________________________________________

    The Runtime, Swing Runtime, and ICAT Debugger components can be 
    installed on a File Allocation Table (FAT) partition. However, for 
    better performance, install them on an High Performance File System 
    (HPFS) or Journaled File System (JFS) partition, which supports long 
    file names. The Toolkit, Toolkit Documentation, Samples, Swing Toolkit, 
    and RMI-IIOP Toolkit must be installed on an HPFS of JFS 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.

      1.1.1  Use of a Single FAT Partition
      ______________________________________________________________________ 

      If you have only one hard disk with a single FAT partition, you have 
      these options:

        o  Leave your system as it is and install only the Runtime
           component and, optionally, the ICAT Debugger component or Swing 
           Runtime component.

        o  Format the FAT partition for HPFS or JFS and reinstall all 
           software.
     
        o  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.

    
       Note:  In this document, the term partition refers to any
              physical or logical drive.
   
    1.2  Making a Copy of Your Current CONFIG.SYS File
    ______________________________________________________________________

    Before installing the Developer Kit, 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.3  Disk Space Requirements
    ______________________________________________________________________

    IBM OS/2 Warp Developer Kit, Java(TM) Edition consists of the 
    following components: 

      Runtime, including Internationalization Support        15.0 MB
      Times New Roman MT 30 Unicode Font                     13.0 MB
      Toolkit                                                 4.0 MB
      Toolkit Documentation                                   8.0 MB
      Samples                                                 3.0 MB
      ICAT Debugger for OS/2 Java                            13.0 MB
      Swing Runtime                                           5.0 MB
      Swing Toolkit                                          35.0 MB
      RMI-IIOP Toolkit                                        2.0 MB
      _________________________________________________      ________
                                   Total installed size      98.0 MB

    You should ensure that sufficient disk space is available 
    before installing.      
                    
    1.4  Hardware Requirements
    ______________________________________________________________________

    o  A minimum of 32 MB of random access memory (RAM) generally provides 
       the best results when running the Developer Kit applications and 
       applets. 
       
    o  IBM strongly recommends using an Intel(R) Pentium(R) (or comparable) 
       processor or higher for all OS/2 systems. 

    o  The Developer Kit specification requires 256-color mode (or greater). 
       The Developer Kit does not support Java applications and applets 
       using the Abstract Window Toolkit (AWT) in 16-color mode.
      
    1.5  FixPaks   
    ______________________________________________________________________	    

    The following considerations apply:       
 
    Required FixPak level for DBCS (Japanese, Traditional Chinese, 
    Simplified Chinese, or Korean) Languages:
      o  OS/2 Warp 3       WX03006
      o  OS/2 Warp 4       FX00505          
           
    To use the Unicode Font support on OS/2 Warp Server and OS/2 Warp 3: 
      o  Single-Byte Character Set Languages (SBCS)    FixPak 30 or higher
      o  For DBCS Languages                            FixPak WX03006

    To use the euro in Java applications and applets:
      o  OS/2 Warp                                     FixPak 6 or higher
      o  OS/2 Warp Server or OS/2 Warp 3               FixPak 35 or higher  
     
    Note:  The display and code conversion of the euro are supported on 
           the code pages containing the euro. 
           
           If you want to input the euro, the SBCS version of OS/2 is 
           required. The U.S. International keyboard, UX103, supports 
           input of the euro, but a standard English keyboard does not. 
           In all cases, if you do not have a keyboard that supports 
           input of the euro, you are able to display it, 
           but you are not able to input it. 
     
    For information about downloading a particular FixPak, visit the IBM 
    FixPak Web site at: 
  
      http://ps.software.ibm.com/pbin-usa-ps/getobj.pl?/pdocs-usa
      /otherservices.html

    1.6  Installing FixPaks after the Developer Kit
    _____________________________________________________________________
             
      o  Installing from Diskettes in other languages:       
         The Developer Kit replaces base operating system modules 
         as part of installation. When you install a FixPak to your 
         OS/2 system after installing the Developer Kit, you are 
         normally prompted if you attempt to replace a module that 
         is newer than the one on the FixPak.  

         However, if you install the FixPak by booting from the FixPak 
         diskettes when this condition exists, you are not prompted. 
         This could result in one or more modules being regressed. 
         Either do not install the FixPak by booting from the diskettes, 
         or back up the base OS/2 modules before installing the FixPak 
         and replace them after installing the FixPak.

      o  On OS/2 Warp 4:
         If you want to install a FixPak prior to FixPak 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.

         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 the Developer Kit after 
              installing the FixPak.       
        
      o  On OS/2 Warp Server or OS/2 Warp 3:
         If you install FixPak 30 or greater (or WX03006 for DBCS), and 
         you want to use the Unicode Font Support, you must reinstall 
         the Runtime and Times New Roman MT 30 Unicode Font Components.
        
    1.7  Replacing Previous Versions of Java 1.1.x 
    ______________________________________________________________________
    
    The Developer Kit replaces all previous versions of Java 1.1.x for 
    OS/2 Warp. However, it will coexist with another version of the 
    Developer Kit if you install it on another drive.    

    If you do not uninstall the previous version, the installation program 
    will replace it with the Developer Kit. 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 warning you 
    that this component will be downlevel and then lets you choose to 
    upgrade the component.
       
    1.8  Backing Up Base OS/2 Files 
    ______________________________________________________________________

    The Developer Kit updates base operating system modules as part of 
    the installation of the Runtime component. Uninstalling the Developer 
    Kit 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. 

    A complete list of new and changed base modules is included in the 
    section "List of OS/2 Base Modules Changed or Added by the Developer 
    Kit" of this README.

    1.9  Netscape Navigator 2.02 Refresh and Java 1.1.x
    ______________________________________________________________________

    If you have the latest Netscape Navigator 2.02 refresh and it is using 
    Java 1.1.x, and you uninstall Java 1.1.x, Netscape Navigator prevents 
    you from installing the Developer Kit because it looks for the previous 
    Java 1.1.x.

    To recover, you must remove all references to Java 1.1.x from the 
    CONFIG.SYS file and reboot.       

    1.10  Running Netscape Communicator 4.04 While Installing the Developer 
          Kit    
    ______________________________________________________________________

    You will not be able to install the Developer Kit if you are running
    Netscape Communicator 4.04 while executing the INSTALL command. You 
    must close down Netscape Communicator 4.04 and then execute the INSTALL 
    command.

    1.11  Netscape Communicator 4.04 and the JIT Compiler
    ______________________________________________________________________

    To run applets using Netscape Communicator 4.04, you must have the
    just-in-time (JIT) compiler turned on. If you want to run applets 
    using Netscape Communicator 4.04 and have the JIT turned off, you 
    will need the latest refresh level of Netscape Communicator 4.04. 
    For information on the latest refresh level, visit the following 
    Web site:

      http://ps.software.ibm.com             

    1.12  Java Integration Layer for Netscape Communicator 4.04
    ____________________________________________________________________

    If you installed Netscape Communicator 4.04 after the Developer Kit, 
    you will need to copy the Java Integration Layer (JIL) file (found in 
    the Developer Kit's \java11 directory) over to the Netscape 
    Communicator 4.04 directory. 
  
       1.  Create a 118 subdirectory under x:\Netscape\program\java\classes. 
           
           x is the drive where you installed Netscape.

      2.  Go to the directory that you installed the Developer Kit. 
          Copy the 118.zip file from x:\JAVA11\NS subdirectory to 
          x:\Netscape\Program\Java\classes.

      3.  Restart Netscape 4.04.		   


  2.0  INSTALLING THE DEVELOPER KIT
  ________________________________________________________________________
 
  The following sections give you information on installing the Developer
  Kit.
  
    2.1  Installing the Developer Kit Through the GUI
    ________________________________________________________________________

    You can install the Developer Kit using either the desktop method or 
    the OS/2 command prompt method. 
                        
      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. Double-click the INSTALL.EXE object to start the 
           installation program.

      The INSTALL.EXE command brings up a Graphical User Interface (GUI) 
      with eleven buttons specifying the languages you can install the 
      program in. Click the language you prefer and the installation 
      program will lead you through the installation steps. 

      A Developer Kit for OS/2 folder is created in the Programs folder 
      on OS/2 Warp 4 and on the Desktop in OS/2 Warp Server and OS/2 
      Warp 3.

      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 from the Developer Kit folder to remove the 
      Java files and subdirectories from the directory where they were 
      extracted. Files and subdirectories not extracted from the Developer 
      Kit are not erased.

      2.1.2  OS/2 Command Prompt Method
      ____________________________________________________________________

      To start installation, make sure that you are in the directory 
      where the Developer Kit files were extracted. At the OS/2 command 
      prompt, type: 

        INSTALL
       
      The install command brings up a GUI with eleven buttons specifying 
      the languages you can install the program in. Click the language you 
      prefer and the installation program leads you through the installation 
      steps. 

      A Developer Kit for OS/2 folder is created in the Programs folder 
      on OS/2 Warp 4 and on the Desktop in OS/2 Warp Server and OS/2 
      Warp 3.

      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 from the Developer Kit folder to remove the 
      Java files and subdirectories from the directory where they were 
      extracted. Files and subdirectories not extracted from the Developer 
      Kit are not erased.
    
      2.1.3  Components Not Selectable During Installation
      ____________________________________________________________________

      If you are using the GUI to install the Developer Kit and components
      are not selectable, you might not have downloaded and extracted the 
      ZIP file containing the component you need. Return to the Software 
      Choice catalog page and download the self-extracting ZIP file that 
      you need.

      The Web site address for the Software Choice catalog is:

        http://service.boulder.ibm.com/asd-bin/doc/index.htm
       
      2.1.4  Recovering from a Failed Installation
      ____________________________________________________________________

      If your installation of the Developer Kit 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 is 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. 
      (where x is the boot drive) To delete the object, click the object 
      using the right mouse button and click Delete on  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.4.1  Cannot Remove the Install Object
      __________________________________________________________________

      If after following the instructions listed above in, "Recovering 
      from a Failed Installation," the install object was not removed, do 
      the following:

        1.  Go to your OS/2 command prompt.
        2.  Change to the boot drive, and then change to the os2\install
            directory.        
        3.  Remove the Java 1.1. for OS!2 directory and all subdirectories.
        4.  Reboot.
      
    2.2  Unattended (CID) Installation Method
    ______________________________________________________________________

    Note: Feature Install version 1.2 or higher is required for CID 
          installations. 

    Unattended or CID installations of the Developer Kit 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 Developer Kit response file 
    (JAVA118.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. 

      2.2.1  Modifying the CID Response File
      ____________________________________________________________________

      Where appropriate, 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.

        The component names are:

          Runtime   	   -     Java Runtime
          Unicode   	   -     Internationalization Support, part of Java Runtime
                      	         Environment
          Unifont   	   -     Times New Roman MT 30 Unicode Font	
          NSFiles   	   -     Netscape Bridge to run Developer Kit applets
          TTengine  	   -     Updated TrueType engine, required for the Unicode Font
          Toolkit   	   -     Toolkit
          TlktDoc   	   -     Toolkit Documentation
          Samples   	   -     Samples
          Debugger  	   -     OS/2 ICAT Debugger for Java
          Swing Runtime    -     Swing Runtime
          Swing Toolkit	   -     Swing Toolkit
	  RMI-IIOP Toolkit -     RMI-IIOP Toolkit 
         
      If you want to install the Japanese Toolkit Documentation, add  
      java11.NLVDest=jp to the CID.RSP file. 
      
      2.2.1.1  Configuration Components
      ____________________________________________________________________

      There is a configuration component associated with each 
      installable component. The CID.RSP file is originally set to 
      install all components. You can 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. 

      The configuration 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.2.1.2  Installation Drives of the Components
      ____________________________________________________________________

      The Runtime package is always installed in the \JAVA11
      directory on the target drive and is a prerequisite for the
      Toolkit, Samples, Swing Runtime, Swing Toolkit, RMI-IIOP Toolkit, 
      and Debugger components. 

      The RMI-IIOP Toolkit is installed in the drive you select under 
      \JAVA11\rmi-iiop. The Swing Runtime and Swing Toolkit are installed 
      in the drive you select under \Swing.

      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 MT 30 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, set the following 
      variables as shown:

        debugger.selection=1
        debuggerconfig.selection=1
        debuggerurls.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 lets 
      you choose to upgrade the component.

      To suppress this confirmation window, along with any others
      encountered during installation, set the following variable 
      as shown:

        java11.continue=UNATTENDED

      2.2.2  Starting the Unattended Installation
      ____________________________________________________________________
 
      The CID.CMD file contains a sample CLIFI command for a CID 
      installation. The installation process has been modified to include 
      a multilingual installation; therefore, you must specify your language 
      variable in the CID.RSP files. The language variables are as follows:

        br = Portuguese, Brazilian Version
        fr = French
        de = German
        it = Italian
        jp = Japanese
        ko = Korean
        cn = Simplified Chinese
        tw = Traditional Chinese
        es = Spanish
        sv = Swedish 
        en = English 

      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:\xx\java118.rsp /b:c: /s:d:\tmp\xx
        /l1:ciderr.log /l2:cidhist.log

        where:
           xx             Specifies the preferred language variable
           /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 Developer Kit 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.3  TME-Architected CID Installation Method
    ______________________________________________________________________

    A JAVA118.ADF file is provided for use with Tivoli(TM) 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 the section 
    "Modifying the CID Response File" of this README.

    You also need to modify your JAVADF.CMD file to identify the 
    preferred language variable:
   
      'clifi /a:c /r:'src'\xx\java118.rsp /r2:'src'\cid.rsp /b:c: 
      /s:'src'\xx /l1:'log1' /l2:'log2
            
      where xx is the preferred language variable  

    2.4  Installing the Developer Kit on WorkSpace On-Demand
    ______________________________________________________________________

    The WorkSpace On-Demand product includes Java 1.1.1 for OS/2 Warp. 
    You can install the Developer Kit on WorkSpace On-Demand servers and 
    clients to upgrade from Java 1.1.1 for OS/2 Warp.  

      2.4.1  Installing the Developer Kit on a WorkSpace On-Demand Server
      ____________________________________________________________________

      To install the Developer Kit on a WorkSpace On-Demand server, use 
      the GUI. See the section "Installing the Developer Kit through the 
      Graphical User Interface (GUI)" of this README for instructions on 
      using the GUI to install. 

      2.4.2  Installing the Developer Kit on a WorkSpace On-Demand Client
      ____________________________________________________________________

      Installation of the Developer Kit on a WorkSpace On-Demand Client is 
      done as an unattended (CID) installation. You can use the 
      instructions in the section "Unattended (CID) Installation Method" 
      of this README and use the CID.CMD and WSOD.RSP files that are 
      included in the Developer Kit installation package. See below for 
      installation requirements.

        2.4.2.1  Requirements for Installation on a WorkSpace 
                 On-Demand Client
        __________________________________________________________________

        Before you can install the Developer Kit for a WorkSpace On-Demand 
        client, Java 1.1.x must already be installed. If the Times New 
        Roman MT 30 Unicode Font (the Unifont component) is selected for 
        installation, it must have been previously installed with WorkSpace 
        On-Demand. If this component was not previously installed, the 
        installation is completed without transferring files. In this case, 
        the wpinstal.log shows that installation completed successfully but 
        no files are transferred.

        2.4.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 "Starting the Unattended Installation"
             of this README:
             
             o  Replace /s:d:\tmp\xx in the CID.CMD file with the drive
                and directory where you unzipped the install package. 
         
                where xx is the preferred language variable 
 
             o  Be sure that /b:c in the CID.CMD file points to the client 
                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 of the files you need.

          2.4.2.3  Multiple Releases of Workspace 
                   On-Demand on the Same Server
          __________________________________________________________________          

          If you have multiple releases of Workspace On-Demand on the same
          server, you will need to comment out the java11.cid=WSOD line by 
          inserting a # character (see example below) and add the line 
          java11.TARGET indicating the WorkSpace On-Demand client image you
          want to upgrade.
 
            #java11.cid=WSOD
            java11.TARGET=x:ibmlan\rp\bb10.en
            
            where x is the directory path 
          
          2.4.2.4  Installing Additional Developer 
                   Kit 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.4.2.5  The JIT Compiler and Workspace On-Demand
          __________________________________________________________________
       
          On a Workspace on Demand system, the following command is added 
          to the CONFIG.SYS file:

            set java_compiler=xxx

          This command turns off the just-in-time (JIT) compiler. To turn 
          the JIT compiler on, remove the command listed above from 
          from your CONFIG.SYS file. You can find and edit the file 
          based on the following two options:

          From the server for a specific user, the CONFIG.SYS file is 
          located in the following drive and directory:
        
            [rpldrive]:\ibmlan\rpl\machines\[machine class]\config.sys

          To modify the default CONFIG.SYS for each machine created 
          using the individual machine's class, the CONFIG.SYS file is 
          located in the following drive and directory::

            [rpldrive]:\ibmlan\rpl\machines\BBX0.xx\[machine name]\config.sys
          
          Where:
 
            o  [rpldrive] is the Request Parameter List
            o  BBXO is the version of Workspace on Demand 
                 -  either BB10 for Workspace on Demand, Version 1
                 -  either BB20 for Workspace on Demand, Version 2
            o  xx is the country code        

    2.5  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 Developer 
    Kit 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 the Developer Kit.

    Use one of the following methods to install the Developer Kit using 
    NVDM/2.

      2.5.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:\xx\java118.rsp /b:c: /s:d:\tmp\xx
        /l1:ciderr.log /l2:cidhist.log"

        where xx is the preferred language variable 

      This method requires you to modify the profile whenever the
      source directory or log file names are changed. Alternatively, 
      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)\xx\java118.rsp
          /b:c: /s:$(SourceDir\xx) /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.6  Remote IPL Installation 
    ______________________________________________________________________

    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 Developer Kit installation files on the 
         remote IPL server.
      2. Run the GENFIRPL command. (See the section "Creating Response 
         Files" for information.)
      3. Run the CLIFI command for one remote IPL client. (See
         the section "Starting the Remote IPL Installation" 
         for information.)
      4. Modify the client FIT file (See the sections "Updating Files 
         for Feature Install" and "Running the Java Samples from a Remote 
         IPL Client.")

    Note: You cannot uninstall the Developer Kit in the remote IPL 
          environment. 
        
      2.6.1  Creating Response Files 
      __________________________________________________________________

      After placing the extracted Developer Kit 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 JAVA118.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\xx  /r:c:\ibmlan\rpl
          /u:c:\ibmlan\rpluser  /f:c:\javacode\xx\java118.rsp
          /c:client_name  /b:x:
           
         where:
      
           xx   Specifies the preferred language variable
           /m   Specifies the directory containing the Developer Kit 
                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 Developer Kit 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.6.2  Modifying the JAVA118.RSP File
      __________________________________________________________________

      The JAVA118.RSP file defaults to installing all the components of 
      Developer Kit. You can modify this response file to explicitly set 
      which components you want to install. Be sure to download and 
      extract all of the files you need before you start the installation. 

      You need to use a text editor that handles lines greater than 255 
      bytes, 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 JAVA118.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
        Unifont           -	 Times New Roman MT 30 Unicode Font	
        NSFiles           -	 Netscape Bridge to run Developer Kit applets
        TTengine          -      Updated TrueType engine, required for the Unicode Font
        Toolkit           -      Toolkit
        TlktDoc           -      Toolkit Documentation
        Samples           -      Samples
        Debugger          -      OS/2 ICAT Debugger for Java
        Swing Runtime     -      Swing Runtime
        Swing Toolkit     -      Swing Toolkit
        RMI-IIOP Toolkit  -      RMI-IIOP Toolkit

      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 JAVA118.RSP file, as shown:

        runtime.selection=1
        runtimeconfig.selection=1
        runtimeurls.selection=1
        Unicode.selection=1
        Unicodeconfig.selection=1
        NSfiles.selection=1
        Jil118.selection=1
        toolkit.selection=0
        toolkitconfig.selection=0
        toolkiturls.selection=0
        tlktdoc.selection=0
        tlktdocconfig.selection=0
        tlktdocurls.selection=0
        samples.selection=0
        samplesconfig.selection=0
        samplesurls.selection=0
        unifont.selection=1
        unifontconfig.selection=1
        TTengine.selection=1
        TTengineconfig.selection=1
        SwingRuntime.selection=0
        SwingRuntimeconfig.selection=0
        SwingToolkit.selection=0
        SwingToolkitconfig.selection=0
        RMIIIOPToolkit.selection=0
        RMIIIOPToolkitconfig.selection=0

      Note:  There is a configuration component associated with
             each installable component. The configuration 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.6.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.6.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:\xx\java118.rsp

        where: 
             
               xx is the preferred language variable 
               
               /r is the fully qualified name of the remote IPL 
                  client's response file, as specified on the 
                  GENFICMD command

      2.6.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 the 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.6.5.1  Issuing a Trust on WorkSpace On-Demand
        ______________________________________________________________

        If you are issuing a trust to connect to a Web server, the 
        IDENTITYDB.OBJ file needs to be read/write. Add the following 
        to the FIT file to make the connection:

          x:\JAVA11\WEBLOGS \\server_name\WRKFILES\client_name\JAVA11\WEBLOGS
          x:\JAVA11\HOTJAVA \\server_name\WRKFILES\client_name\JAVA11\HOTJAVA 
          Z:\JAVA11\IDENTITYDB.OBJ  \\server\WRKF\client\JAVA11\IDENTITYDB.OBJ

        This could also be entered in the default FIT file as part of 
        the installation of Java 1.1.x for WorkSpace On-Demand when running 
        the WSOD.CMD command.

      2.6.6  Upgrading Java 1.1.x to the 
              Developer Kit in the Remote IPL Environment
      __________________________________________________________________

      To upgrade Java 1.1.x to the Developer Kit in the 
      remote IPL environment:

        1. Place the extracted Developer Kit installation files on the 
           remote IPL server.
        2. Run the GENFIRPL command. (See "Creating Response Files" 
           in this README for more information.)
        3. Run the CLIFI command for one remote IPL client. 
           (See "Starting the Remote IPL Installation in this README 
           for more 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.x installation.   
  
  3.0  AFTER YOU INSTALL
  ______________________________________________________________________

  The following sections provide additional information you might need 
  after you install the Developer Kit. 
          
    3.1  Additional Sources of Information
    ____________________________________________________________________
 
    The objects in the following list are displayed in the Developer Kit
    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. 

      o  IBM Center for Java Technology:
         http://ncc.hursley.ibm.com/javainfo/hurindex.html

      o  Running Java:
         x:\JAVA11\runtime.htm

      o  Configure Applet Viewer:
         x:\JAVA11\cnfgappl.htm

      o  Java Documentation:
         http://www.javasoft.com/doc.html

      o  Java Developer's Kit for OS/2:
         x:\JAVA11\index.html

      o  Java Toolkit:
         x:\JAVA11\toolkit.html

      o  Java API:
         x:\JAVA11\docs\xx\api\API_users_guide.html

      o  ICAT Debugger for OS/2 Java:
         x:\JAVA11\ICATJAVA\help\icatjvo.htm

      where:
      x is the partition where you installed the Developer Kit
      xx is the preferred language

    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 these four 
    objects. 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 directories.

    3.2  Installing Additional Components
    ____________________________________________________________________

    After the initial installation of the Developer Kit 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.    

    3.3  Java Database Connectivity (JDBC)-Open Database Connectivity 
         (ODBC) Bridge Not Provided
    ____________________________________________________________________
 
    The Developer Kit provides JDBC, 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 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. The Developer Kit does not 
    provide a JDBC-ODBC bridge.

    3.4  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.

    3.5  Modifying Font Properties Files Not Supported
    ____________________________________________________________________

    Modifying the font properties files provided with the 
    Developer Kit is not supported. 
     
    3.6  Time Problems 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:

      o  Go to the General page in the TCP/IP Configuration notebook.
         Set the timezone field, using the online help provided.
      
      o  Edit the CONFIG.SYS file and add or change the SET TZ= statement.   

    3.7  LIBPATH Changes That Could Affect Your System
    ____________________________________________________________________

    If 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 includes OS/2 base 
    DLL modules in a different directory. This change does not affect 
    the Toolkit, but (depending on which DLL module is first in the 
    LIBPATH) could affect other products that include OS/2 base DLL 
    modules.   
    
    3.8  Verification Exception
    ____________________________________________________________________

    If you are running an application that is minimized and receive the error 
    message:

      java.lang.verifyerror exception

    there are two options:

      o  Inform your application vendor. Your vendor might have an updated
         version that will run with the Developer Kit (version 1.1.8 ). 
      o  Run the Developer Kit using the -noverify option from either your
         OS/2 command prompt or browser. 
  
    3.9  Using the OS/2 High Memory Support to Increase the Java Heap 
         Size
    ____________________________________________________________________  

    In a standard OS/2 environment, the maximum virtual address space is 
    available to an application is 512 MB, and the memory available for 
    the Java heap size is limited to approximately 256 MB. This 
    restriction can be modified by using OS/2 High Memory Support (OS/2 
    HMS). OS/2 HMS increases the maximum virtual address space available 
    to an application to 3 GB.

    The following platforms support OS/2 HMS:
         
      o  OS/2 Warp Server Advanced SMP Feature (with FixPak 32 or higher)
      o  WorkSpace On-Demand servers 
      o  OS/2 Warp Server for e-business 

    The following platforms do not support OS/2 HMS:
    
      o  OS/2 Warp Server 
      o  OS/2 Warp Server Advanced 
      o  WorkSpace On-Demand clients     
      o  OS/2 Warp 4
      o  OS/2 Warp 3
      o  OS/2 Warp Connect

      3.9.1  Enabling OS/2 HMS
      __________________________________________________________________

      The available High Memory is controlled by the VIRTUALADDRESSLIMIT
      setting in the CONFIG.SYS file. The value is specified in MBs in 
      the CONFIG.SYS file. For example:

        VIRTUALADDRESSLIMIT=2048

     The smallest value allowed is 512 MB. This ensures compatibility 
     with previous versions of OS/2 that allowed access to 512 MB.  
     Values in excess of 512 MB will reduce the number of processes that 
     can concurrently run on a system.
      
      3.9.2  Enabling Java Heap Size To Use OS/2 HMS
      __________________________________________________________________

      To indicate to the Java Virtual Machine (JVM) that it should 
      attempt to place its heap into OS/2 HMS, set the following 
      environment variable:

        SET JAVA_HIGH_MEMORY=1

      If OS/2 HMS is not available this option will be ignored and the
      heap will be allocated from the standard address space.

      3.9.3  Limitations When Using OS/2 HMS
      __________________________________________________________________

      If the Java heap is placed in OS/2 HMS, the objects allocated from
      it will not be accessible to 16-bit code. This is only a problem if 
      a Java application has native method DLLs that are either compiled 
      with a 16-bit compiler or call other DLLs that contain 16-bit code.

      OS/2 TCP/IP, prior to version 4.1, has this limitation. OS/2 TCP/IP 
      4.1 or later must be installed if OS/2 HMS heaps are used.

    3.10  Enhanced BigDecimal Class
    ____________________________________________________________________       

    This release introduces an enhanced BigDecimal class 
    (com.ibm.math.BigDecimal) for Java programming. It is provided 
    (with its supporting class MathContext) as an alternative to the 
    java.math.BigDecimal class.

    The new class is available in the math.jar file located in the 
    x:\JAVA11\lib\ directory. The math.jar file is automatically added 
    to the CLASSPATH. (x is the drive where you installed the 
    Developer Kit)

    If you are using the java.math.BigDecimal class in a Java program and 
    you want to access the new class, you must change the import statement 
    in your source code as shown below. 
    
      Change:  import java.math.*; 
      To:      import com.ibm.math.*;

    You do not need to change any other code.

    API documentation is included in the x:\JAVA11\docs\api.bigdecimal
    subdirectory. A small example program (decdemo.java) and a README 
    (README.dec) are available in the x:\JAVA11\examples\bigdecimal 
    subdirectory. (x is the drive where you installed the Developer 
    Kit).

  4.0  DOUBLE-BYTE CHARACTER SET CONSIDERATIONS
  _______________________________________________________________________

    The following sections describe known DOUBLE-BYTE CHARACTER SET 
    (DBCS) considerations.

    4.1  Installation Panel Text Missing or Too Long in DBCS Countries
    ____________________________________________________________________

    When installing the Developer Kit 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 or Netscape Communicator 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 the Developer Kit again, the text should be 
    displayed correctly. 

    4.2  Korean OS/2 Users Need PTF for Updated Fonts
    ____________________________________________________________________
 
    If you want to install the Developer Kit on an OS/2 system that 
    supports Korean, you must first apply PTF PK0817 to your system. 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 Developer Kit.

    4.3  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. At an OS/2 command prompt and where C: is the boot drive, 
         start the Selective Install program by typing:

           C:\OS2\INSTALL\INSTALL
         
         A panel titled "System Configuration" is displayed.

      2. Continue to the OS/2 Setup and Installation panel by
         clicking the Next buttons (for OS/2 Warp 4.0) or the
         OK button (for OS/2 Warp Server 4.0 or OS/2 Warp 3).

      3. On the OS/2 Setup and Installation panel, select the
         TrueType Fonts check box.

      4. Click 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, or OS/2 Warp 3) into the CD drive.

      7. Click OK on the Source Directory panel.

      The appropriate fonts should be installed. Restart your system
      when the font installation is completed. 
    
    4.4  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 zero (0) 
    through nine (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.5  Installing Japanese FixPak 2 (FX00002) after OS/2 Warp 4
         Japanese version (without VoiceType) and the Developer Kit
    ____________________________________________________________________

    If you plan to install Japanese FixPak 2 (FX00002) over OS/2 Warp 4 
    Japanese version (without VoiceType), you should do it before 
    installing the Developer Kit. Otherwise, OS/2 might not reboot. 
    However, if you need to install the Japanese FixPak 2 on OS/2 Warp 4
    Japanese version (without VoiceType), after installing the Developer 
    Kit, do the following:
    
    Before you apply Japanese FixPak 2, 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. Restore the files with the ones you saved (listed above) before
         installing the Developer Kit. At an OS/2 command prompt, copy 
         these files back into the \os2\dll subdirectory.
      5. At the OS/2 command prompt, type: 

           EXIT
         
         and press Enter. The system now restarts.

     Note: OS/2 Warp 4 Japanese version (with VoiceType) includes
           FixPak 2 (FX00002).

    4.6  Japanese Environment Settings on OS/2 Warp 4 Japanese Version
    ____________________________________________________________________

    Use the following Japanese environment settings for OS/2 Warp 4
    Japanese version:

      o  Codepage                932
      o  ShiftJIS code           New JIS

    4.7  Required Fonts on OS/2 Warp Japanese Version
    ____________________________________________________________________

    To run the Developer Kit, 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:

      o  The Install/Remove folder in the System Setup folder on OS/2
          Warp 4 systems

      o  The System Setup folder on OS/2 Warp Server and OS/2 Warp 3 
         systems

    4.8  Modifying the CONFIG.SYS File for DBCS Languages on OS/2 
         Warp 3 Connect 
    ____________________________________________________________________

    Verify (and change if necessary) that the language variable is set
    as follows: 
    
      For Chinese:     SET LANG=zh_CN    
      For Japanese:    SET LANG=ja_JP
      For Korean:      SET LANG=ko_KR
      For Taiwanese:   SET LANG=zh_TW       
      
    If it is not set correctly, then the Developer Kit will not be able 
    to find the proper locale.   

  5.0  LIST OF OS/2 BASE MODULES CHANGED OR ADDED BY THE DEVELOPER KIT
  ______________________________________________________________________

  When you install the Developer Kit 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, OS/2 Warp Server,
  or OS/2 Warp 3 at FixPak 30 or higher for SBCS and FixPak 
  WX03006 or higher for DBCS:

        \os2\dll\truetype.dll

  The following file contains Monotype Corporation's Times New 
  Roman MT 30 TrueType Unicode Font. If you have previously installed 
  a font with the same file name, this file replaces it:

        \os2\dll\tnrmt30.ttf

  6.0  UNINSTALLING THE DEVELOPER KIT
  ______________________________________________________________________
   
  You can uninstall the Developer Kit using the following methods:

    6.1  Desktop Method
    ____________________________________________________________________

    To uninstall using the Remove the Developer Kit object, follow these
    steps:

      1. Open the OS/2 System folder.
      2. Open the System Setup folder.
      3. If you are uninstalling from OS/2 Warp 4, open the Install/Remove 
         folder.
      4. Open the Uninstall Features folder.
      5. Select the Remove the Developer Kit for OS/2 object to start the
         uninstall program.
       
    To restore base OS/2 files that were saved before installing
    the Developer Kit, see "Restoring Base OS/2 Files" in this README. 

    6.2  OS/2 Command Prompt Method
    ______________________________________________________________________

    To start uninstalling, make sure that you are either in the directory 
    where the Developer Kit 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.

    To restore base OS/2 files that were saved before installing
    the Developer Kit, see "Restoring Base OS/2 Files" below. 

    6.3  Uninstalling from WorkSpace On-Demand
    ______________________________________________________________________

    Support for uninstalling the Developer Kit requires access to an 
    inventory object (Java 1.1.8) in the Installed Features directory 
    (\os2\install\installed features). If you install the Developer 
    Kit for both the WorkSpace On-Demand client and the WorkSpace 
    On-Demand server, the Java 1.1.8 inventory object is damaged or 
    replaced.

    To remove the Developer Kit from the client space, reinstall the 
    WorkSpace On-Demand version of Java 1.1.x. This installation will 
    replace the Developer Kit.

    To remove the Developer Kit 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 
    on the boot drive.

    6.4  Performing an Unattended Uninstallation
    ______________________________________________________________________

    To uninstall the Developer Kit, enter the following single-line 
    command at an OS/2 command prompt:

      clifi /a:u /f:"<WP_INSTALLED>" /o:INV_JAVA11 /set:Selection=ALL  

    6.5  Restoring Base OS/2 Files
    ______________________________________________________________________

    In most cases, the base OS/2 files replaced during the installation 
    of the Developer Kit can be used after you uninstall the Developer Kit. 
    If you made copies of the original files, as described in the section  
    "Coexistence with Previous Versions of Java 1.1.x" 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 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. Restore the files with the ones you saved (listed above) before
         installing the Developer Kit. At an OS/2 command prompt, copy 
         these files back into the \os2\dll subdirectory.
      5. At the OS/2 command prompt, type: 

           EXIT
         
          and press Enter. The system now restarts.
       
    Note:  If you installed the Developer Kit over Java 1.1.x and you 
           later uninstall the Developer Kit, the CONFIG.SYS file is 
           returned to the Java 1.1.x level.
      
           If you install the Toolkit component of the Developer Kit 
           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.
  
  7.0  NOTICES
  ________________________________________________________________________

  This edition applies to version 1.1.8 of the IBM OS/2 Warp Developer 
  Kit, Java(TM) Technology Edition and to all subsequent releases and 
  modifications until otherwise indicated in new editions.

  Copyright International Business Machines Corporation 1999. All rights 
  reserved. 
  
  Note to U.S. Government Users Restricted Rights --Use, duplication 
  or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 
  
  Consult your local IBM representative for information on the products 
  and services currently available in your area. Any reference to an IBM 
  product, program, or service is not intended to state or imply that 
  only that IBM product, program, or service may be used. Any functionally 
  equivalent product, program, or service that does not infringe any IBM 
  intellectual property right may be used instead. However, it is the 
  users responsibility to evaluate and verify the operation of any 
  non-IBM product, program, or service.

  IBM may have patents or pending patent applications covering subject 
  matter in this document. The furnishing of this document does not give 
  you any license to these patents. You can send license inquiries, in 
  writing, to: 

    IBM Director of Licensing
    IBM Corporation
    North Castle Drive
    Armonk, NY  10504-1758>
    U.S.A.

  For license inquiries regarding double-byte (DBCS) information, 
  contact the IBM Intellectual Property Department in your country or 
  send inquiries, in writing, to: 

    IBM World Trade Asia Corporation Licensing
    2-31 Roppongi 3-chome, Minato-ku
    Tokyo 106, Japan
 
  The following paragraph does not apply to the United Kingdom or any
  other country where such provisions are inconsistent with local law:
 
    INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS 
    PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER 
    EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE 
    IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR 
    FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow 
    disclaimer of express or implied warranties in certain 
    transactions, therefore, this statement may not apply to you.  

  This information could include technical inaccuracies or
  typographical errors.  Changes are periodically made to the 
  information herein; these changes will be incorporated in new editions
  of the information.  IBM may make improvements and/or changes in the
  product(s) and/or the program(s) described in this information at any
  time without notice.  

  Any references in this information to non-IBM Web sites are provided 
  for convenience only and do not in any manner serve as an endorsement 
  of those Web sites. The materials at those Web sites are not part of 
  the materials for this IBM product and use of those Web sites is at 
  your own risk.

  IBM may use or distribute any of the information you supply in any 
  way it believes appropriate without incurring any obligation to you.

  Licensees of this program who wish to have information about it 
  for the purpose of enabling (i) the exchange of information between 
  independently created programs and other programs (including this one) 
  and (ii) the mutual use of the information which has been exchanged, 
  should contact:

    JTCMAIL@uk.ibm.com
    [Hursley Java Technology Center (JTC) contact]

  Such information may be available, subject to appropriate terms and 
  conditions, including in some cases, payment of a fee.  

  The licensed program described in this document and all licensed 
  material available for it are provided by IBM under terms of the 
  IBM Customer Agreement, IBM International Program License Agreement 
  or any equivalent agreement between us. 

  Any performance data contained herein was determined in a controlled 
  environment. Therefore, the results obtained in other operating 
  environments may vary significantly. Some measurements may have been 
  made on development-level systems and there is no guarantee that these
  measurements will be the same on generally available systems. 
  Furthermore, some measurement may have been estimated through
  extrapolation. Actual results may vary.  Users of this document
  should verify the applicable data for their specific environment.

  Information concerning non-IBM products was obtained from the
  suppliers of those products, their published announcements or other
  publicly available sources. IBM has not tested those products and
  cannot confirm the accuracy of performance, compatibility or any other
  claims related to non-IBM products.  Questions on the capabilities of
  non-IBM products should be addressed to the suppliers of those
  products.  

  All statements regarding IBM's future direction or intent are subject 
  to change or withdrawal without notice, and represent goals and  
  objectives only. 

  All IBM prices shown are IBM's suggested retail prices, are current 
  and are subject to change without notice.  Dealer prices may vary.

  COPYRIGHT LICENSE: 

  This information contains sample application programs in source
  language, which illustrate programming techniques on various
  operating platforms. You may copy, modify, and distribute these
  sample programs in any form without payment to IBM, for the purposes
  of developing, using, marketing or distributing application programs
  conforming to the application programming interface for the operating
  platform for which the sample programs are written. 

  These examples have not been thoroughly tested under all conditions.  
  IBM, therefore, cannot guarantee or imply reliability, serviceability, 
  or function of these programs. You may copy, modify, and distribute 
  these sample programs in any form without payment to IBM for the 
  purposes of developing, using, marketing, or distributing application 
  programs conforming to IBM's application programming interfaces. 

  8.0  TRADEMARKS
  ______________________________________________________________________

  The following terms are trademarks of International Business Machines 
  Corporation in the U.S., or other countries, or both:

         IBM
         OS/2

  Java is a trademark 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.

  Intel and Pentium are registered trademarks of Intel Corporation
  in the United States and other countries.

  Tivoli is a trademark of Tivoli Systems Inc. in the United States, 
  other countries, or both.

  Other company, product, and service names may be trademarks or
  service marks of others.

  (c) Copyright IBM Corporation 1999, All rights reserved.

  ________________________________________________________________________

  END-OF-README-FILE
  ________________________________________________________________________
