  ________________________________________________________________________

  IBM OS/2 Warp Developer Kit, Java(TM) Edition, Version 1.1.7 
  Installation README
  ________________________________________________________________________

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

    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 3 
    OS/2 Warp Connect 

    Note:  Simplified Chinese is not supported on OS/2 Warp 3.

  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 the Developer Kit 
  and provides information about known problems and temporary fixes for 
  them.  References to objects specific to this product are referred to as, 
  Java 1.1.7 objects.
  ________________________________________________________________________
  CONTENTS

     1.0.  BEFORE YOU INSTALL
     1.1.  Making a Copy of Your Current CONFIG.SYS File
     1.2.  Disk Space Requirements
     1.3.  Hardware Requirements
     1.4.  FixPaks   
     1.5.  Installing FixPaks after the Developer Kit
     1.6.  HPFS and FAT Partition Considerations
     1.7.  Coexistence with Previous Versions of Java
     1.8.  Replacing Previous Versions of Java 1.1.x
     1.9.  Backing Up Base OS/2 Files
     1.10. Netscape 2.02 Refresh and Java 1.1.x
     1.11. Running Netscape 4.04 While Installing the Developer Kit    
   
     2.0.  INSTALLING THE DEVELOPER KIT
     2.1.  Installing the Developer Kit Through the Graphical 
           User Interface (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.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.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 for 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.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 JAVA117.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 Java 1.1.6 to the Developer Kit in the 
             Remote IPL Environment
     
     3.0.  UNINSTALLING THE DEVELOPER KIT
     3.1.  Desktop Method
     3.2.  OS/2 Command Prompt Method
     3.3.  Uninstalling from WorkSpace On-Demand     
     3.4.  Performing an Unattended Uninstallation
     3.5.  Restoring Base OS/2 Files   

     4.0.  AFTER YOU INSTALL
     4.1.  Additional Sources of Information
     4.2.  Installing Additional Components
     4.3.  JDBC-ODBC Bridge Not Provided
     4.4.  AWT TextField and TextArea Considerations
     4.5.  Modifying Font Properties Files Not Supported
     4.6.  Time Problems in Java Applets 
     4.7.  LIBPATH Changes That Could Affect Your System
     4.8.  Verification Exception

     5.0.  DOUBLE-BYTE CHARACTER SET (DBCS) CONSIDERATIONS
     5.1.  Installation Panel Text Missing or Too Long in DBCS Countries
     5.2.  Korean OS/2 Users Need PTF for Updated Fonts
     5.3.  TrueType Fonts Must Be Installed on Chinese Systems
     5.4.  Controlling Arabic Number Character Display 
     5.5.  Installing Japanese FixPak 2 (FX00002) over OS/2 Warp 4
           Japanese version (without VoiceType) and the Developer Kit
     5.6.  Japanese Environment Settings on OS/2 Warp 4 Japanese Version
     5.7.  Required Fonts on OS/2 Warp Japanese Version
     5.8.  Modifying the CONFIG.SYS File for Japanese on Warp 3 Connect
     
     6.0.  LIST OF OS/2 BASE MODULES CHANGED OR ADDED BY THE DEVELOPER KIT
     
     7.0.  TRADEMARKS


  1.0.  BEFORE YOU INSTALL
  ________________________________________________________________________
 
  Note:  In this document, the term partition refers to any
         physical or logical drive.
       
         The Runtime package must be installed to use any component other 
         than the Toolkit Documentation.  You cannot install the Toolkit, 
         Samples, or ICAT Debugger unless you are also installing the 
         Runtime component or have previously installed the Runtime 
         component and rebooted the system.

    1.1.  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.2.  Disk Space Requirements
    ______________________________________________________________________

    IBM OS/2 Warp Developer Kit, Java(TM) Edition 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

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

    o  A minimum of 32 MB of random access memory (RAM) provides the best 
       results when running the Developer Kit applications and applets.  
       
    o  IBM strongly recommends using an Intel(R) Pentium (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.4.  FixPaks   
    ______________________________________________________________________	    

    The following considerations apply:       

    To use the Developer Kit on OS/2 Warp 3: 
      o  Single-Byte Character Set Languages (SBCS)     FixPak 32 or higher	
      o  For Japanese, Traditional Chinese, or Korean   FixPak WX03006  
         
    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 Japanese, Traditional Chinese, or Korean   FixPak WX03006
       
    To use the Eurocurrency Symbol (the Euro) in Java applications 
    and applets:
      o  OS/2 Warp 4                                    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 is 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 Eurocurrency symbol, 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.5.  Installing FixPaks after the Developer Kit
    ______________________________________________________________________
             
      o  Installing from Diskettes:       
         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 DBCS equivalent), and 
         you want to use the Unicode Font Support, you must reinstall 
         the Runtime and Times New Roman MT 30 Unicode Font Components.
 
    1.6.  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 these options:

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

           o  Format the FAT partition for HPFS 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.
    
    1.7.  Coexistence with Previous Versions of Java
    ______________________________________________________________________

    IBM OS/2 Warp Developer Kit, Java(TM) Edition, Version 1.1.7 replaces 
    all previous versions of Java 1.1.x for OS/2 Warp.
      
    1.8.  Replacing Previous Versions of Java 1.1.x 
    ______________________________________________________________________
    
    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.9.  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.  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 the 
    section "List of OS/2 Base Modules Changed or Added by the Developer 
    Kit" of this README.

    1.10.  Netscape 2.02 Refresh and Java 1.1.x
    ______________________________________________________________________

    If you have the latest Netscape 2.02 refresh and it is using Java 
    1.1.x, and you uninstall Java 1.1.x, Netscape 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.11.  Running Netscape 4.04 While Installing the Developer Kit    
    ______________________________________________________________________

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

  2.0.  INSTALLING THE DEVELOPER KIT
  ________________________________________________________________________
  
  Note:  The Runtime package must be installed to use any component other 
         than the Toolkit Documentation.  You cannot install the Toolkit, 
         Samples, or ICAT Debugger unless you are also installing the 
         Runtime component or have previously installed the Runtime 
         component and rebooted the system. 
    
    2.1.  Installing the Developer Kit Through 
          the Graphical User Interface (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 GUI with eleven buttons 
      specifying the languages you can install the program in. Click the 
      language your 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 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.

      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 Developer Kit files were extracted.  At 
      an OS/2 command prompt, enter: 

        DELINST

      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 that you believe you downloaded and extracted, you 
      might not have downloaded and extracted the ZIP file containing 
      the component you need.  You need to return to the Software Choice 
      catalog page and download the correct self-extracting ZIP file.  
       
      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 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, click the object with the right mouse button 
      and click Delete on the menu. (Where x is the boot drive.)

      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 in section 2.1.4., 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.1.5.  Unable to Create Feature Install Object 
              on OS/2 Warp Server and OS/2 Warp 3
      ____________________________________________________________________

      If your installation of the Developer Kit fails on an OS/2 Warp 
      Server or OS/2 Warp 3 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.  The fix for the problem is 
      included in FixPaks 33 and higher.  

    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 
    (JAVA117.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
         
      If you want to install the Japanese Toolkit Documentation, add  
      java11.NLVDest=jp to the CID.RSP file. 
       
      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 a configuration component associated with each 
             installable component.  The configuragation 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 package 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 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:

        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 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 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\java117.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 JAVA117.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 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\java117.rsp /r2:'src'\cid.rsp /b:c: 
      /s:'src'\xx /l1:'log1' /l2:'log2
            
      xx is the preferred language variable.   

    2.4.  Installing the Developer Kit 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 the Developer Kit on WorkSpace On-Demand servers and 
    clients to upgrade from Java 1.1.1.  

      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.

        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 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.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. 
         
                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
            
            x is the directory path you choose
          
          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.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\java117.rsp /b:c: /s:d:\tmp\xx
        /l1:ciderr.log /l2:cidhist.log"

        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\java117.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 JAVA117.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\java117.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 JAVA117.RSP File
      __________________________________________________________________

      The JAVA117.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 
      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 JAVA117.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

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

        runtime.selection=1
        runtimeconfig.selection=1
        Unicode.selection=1
        Unicodeconfig.selection=1
        NSfiles.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 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

        /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\java117.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.

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

      To upgrade Java 1.1.6 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.6 installation.    
     
  3.0.  UNINSTALLING THE DEVELOPER KIT
  ______________________________________________________________________
   
  You can uninstall the Developer Kit using the following methods:

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

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

    3.3.  Uninstalling from WorkSpace On-Demand
    ______________________________________________________________________

    Support for uninstalling the Developer Kit requires access to an 
    inventory object (Java 1.1.7) in the Installed Features directory 
    (\os2\install\installed features).  If you install the Developer 
    Kit both for the WorkSpace On-Demand client and the WorkSpace 
    On-Demand server, the Java 1.1.7 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 
    that is on the boot drive.

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

    3.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 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 the Developer Kit. 
      5. At an 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.

  4.0.  AFTER YOU INSTALL
  ______________________________________________________________________

  The following sections provide additional information you might need 
  after you install the Developer Kit. 
          
    4.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\api\API_users_guide.html

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

      x is the partition where you installed Java.

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

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

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

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

    4.5.  Modifying Font Properties Files Not Supported
    ______________________________________________________________________

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

    4.7.  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 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.    
    
    4.8.  Verification Exception
    _______________________________________________________________________

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

      java.lang.verifyerror exception

    there are two options:

      o  Inform your application vendor. Your vendor may have an updated
         version that will run with the Developer Kit (version 1.1.7).  
      o  Run the Developer Kit using the -noverify option from either your
         OS/2 command prompt or browser.  

  5.0.  DOUBLE-BYTE CHARACTER SET (DBCS) CONSIDERATIONS
  _______________________________________________________________________

    The following sections describe known DBCS considerations.

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

    5.2.  Korean OS/2 Users Need PTF for Updated Fonts
    ____________________________________________________________________
 
    If you want to install the Developer Kit on a Korean OS/2 system, 
    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.

    5.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 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, 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 are installed.  Restart your system
      when the font installation is completed. 
    
    5.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.

    5.5.  Installing Japanese FixPak 2 (FX00002) over OS/2 Warp 4
          Japanese version (without VoiceType) and the Developer Kit
    ____________________________________________________________________

    Note:  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.  
    
    Before you apply the Japanese FixPak 2 (after installing the 
    Developer Kit) 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.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

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

    5.8.  Modifying the CONFIG.SYS File for Japanese on Warp 3 Connect 
    ____________________________________________________________________

    Verify that the language variable for Japanese is ja_jp. If it is 
    not set correctly, then the Developer Kit will not be able to find 
    the Japanese locale.    

  6.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 and on OS/2 Warp 
  Server or OS/2 Warp 3 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 and on 
  OS/2 Warp Server or OS/2 Warp 3 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
  
  7.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 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
  ________________________________________________________________________
