home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: Java
/
Java.zip
/
java114.zip
/
readme
< prev
next >
Wrap
Text File
|
1997-11-18
|
79KB
|
1,789 lines
________________________________________________________________________
Java(TM) 1.1.4 for OS/2 Warp Installation README
________________________________________________________________________
Java 1.1.4 for OS/2 Warp provides the Sun Microsystems, Inc. Java
environment on:
OS/2 Warp 4
OS/2 Warp Server Version 4
OS/2 Warp Server Advanced Version 4
OS/2 Warp Server Advanced Version 4 SMP Feature
WorkSpace On-Demand clients and servers
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.
This README guides you through installation of Java 1.1.4 for OS/2 Warp
and provides information on known problems and temporary fixes for them.
________________________________________________________________________
CONTENTS
1. Before You Install
1.1 Disk Space Requirements
1.2 Software Prerequisites
1.2.1 OS/2 Warp Server Systems Require FixPak for Unicode Font Support
1.2.2 Feature Install Required for Installing Java 1.1.4
1.3 HPFS and FAT Drive Considerations
1.4 Coexistence with Prior Versions of Java
1.4.1 Coexistence with Java 1.0.1 and 1.0.2
1.4.2 Replacing Java 1.1.1
1.5 Backing Up Base OS/2 Files Not Restored on Uninstall
1.6 Saving a Copy of CONFIG.SYS
1.7 Minimum Hardware Recommendations
1.8 Installing FixPak 2 on OS/2 Warp 4 Systems after Java 1.1.4
1.9 Installation Panel Text Missing or Too Long in DBCS Countries
1.10 Installing on OS/2 Warp 4 Japanese version (without VoiceType)
1.11 Japanese Environment Setting on OS/2 Warp 4 Japanese version
1.12 Required Fonts on OS/2 Warp Japanese version
2. Installing Java 1.1.4 for OS/2 Warp
2.1 Installing Java 1.1.4 for OS/2 Warp through the Graphical
User Interface (GUI)
2.1.1 Desktop Method
2.1.2 OS/2 Command Prompt Method
2.1.3. "Files Missing" Error During Installation
2.1.4 Recovering from a Failed Installation
2.1.5 Unable to Create Feature Install Object on OS/2 Warp Server
Systems
2.2 Unattended (CID) Installation Method
2.2.1 Modifying the CID Response File
2.2.2 Starting the Unattended Installation
2.2.3 Performing an Unattended Uninstall
2.3 TME-Architected CID Installation Method
2.4 NetView DM/2 Installation Considerations
2.4.1 Put Static Command in NVDM/2 Profile
2.4.2 Customize JAVA114.RSP File
2.5 Remote IPL Installation Considerations
2.5.1 Creating Response Files
2.5.2 Modifying the JAVA114.RSP File
2.5.3 Updating Files for Feature Install
2.5.4 Starting the Remote IPL Installation
2.5.5 Running the Java Samples from a Remote IPL Client
2.5.6 Remote IPL Restrictions
2.6 Installing Java 1.1.4 for OS/2 Warp on WorkSpace On-Demand
2.6.1. Installing Java 1.1.4 for OS/2 Warp for Use on a WorkSpace
On-Demand Server
2.6.2. Installing Java 1.1.4 for OS/2 Warp for a WorkSpace
On-Demand Client
2.6.2.1 Requirements for Installation on a WorkSpace On-Demand Client
2.6.2.2 Modifying the CID.CMD and WSOD.RSP Files
2.6.2.3 Installing Additional Java 1.1.4 Components on the WorkSpace
On-Demand Client
2.6.3 Uninstalling on WorkSpace On-Demand
3. Uninstalling Java 1.1.4 for OS/2 Warp
3.1 Desktop Method
3.2 OS/2 Command Prompt Method
3.3 Restoring Base OS/2 Files
3.4 Entries Left in CONFIG.SYS after Uninstall
3.5. Unattended Uninstall
3.6. Uninstalling on WorkSpace On-Demand
4. After You Install
4.1 Additional Sources of Information
4.2 Installing Additional Components
4.3 Netscape Navigator for OS/2 Considerations
4.4 Class.forName()
4.5 Disabling the Just-In-Time (JIT) Compiler
4.6 Native Methods Need to be Recompiled
4.7 LIBPATH Changes That Could Affect Your System
4.8 Applying OS/2 Service after Installing Java 1.1.4 for OS/2 Warp
4.9 Installing a FixPak on OS/2 Warp Server Systems after Java 1.1.4
4.10 Using 16-Color Mode with Java 1.1.4 for OS/2 Warp
4.11 JDBC-ODBC Bridge Not Provided
4.12 AWT TextField and TextArea Considerations
4.13 Controlling Arabic Number Character Display
4.14 Modifying Font Properties Files Not Supported
4.15 Printing Considerations
4.16 Behavior of Backslash and Tilde in DBCS Countries
4.17 Class Name Case Sensitivity
4.18 Using Java 1.0.2 for OS/2 after Installing Java 1.1.4 for OS/2 Warp
4.19 Problems with Time in Java Applets
4.20 Korean OS/2 Users Need PTF for Updated Fonts
4.21 TrueType Fonts Must Be Installed on Chinese Systems
4.22 Conversion between ShiftJIS and Unicode on OS/2 Warp 4
Japanese version
4.23 Installing Japanese FixPak 2 (FX00002) over OS/2 Warp 4
Japanese version (without VoiceType) & Java 1.1.4
5. List of OS/2 Base Modules Changed or Added by Java 1.1.4 for OS/2 Warp
6. Trademarks
________________________________________________________________________
1. Before You Install
Note: In this document, the term partition refers to any
physical or logical drive.
____________________________
1.1. Disk Space Requirements
Java 1.1.4 for OS/2 Warp consists of the following components:
Runtime, including Internationalization Support 14.0 MB
Toolkit 2.5 MB
Toolkit Documentation 7.4 MB
Samples 2.7 MB
Times New Roman MT 30 Unicode Font 12.9 MB
OS/2 ICAT Debugger for Java 12.8 MB
______________________ _______
Total installed size 52.3 MB
The Runtime component must be installed to use any component
other than Toolkit Documentation.
The Times New Roman MT 30 Unicode Font component can be
installed on OS/2 Warp 4 systems. OS/2 Warp Server systems
must be at a FixPak 30 service level or higher to install the
Unicode Font component.
Ensure that sufficient disk space is available before installing.
Note: Be sure that when you extracted the Java 1.1.4 for OS/2 Warp
files from the original ZIP file, you specified the proper
option on your file extraction utility to create subdirectories.
For pkunzip2 this option is -d. Failure to extract the files
properly results in the installation program failing
while copying files. If you did not use the correct option,
you should extract the files again before you install.
___________________________
1.2. Software Prerequisites
_______________________________________________________________________
1.2.1. OS/2 Warp Server Systems Require FixPak for Unicode Font Support
Users on OS/2 Warp Server systems who want to use the Unicode
Font support should first apply FixPak 30 (or greater). To obtain
access to download a particular FixPak, please contact your
local IBM OS/2 support representative. If you choose to
install the FixPak after installing Java 1.1.4 for OS/2 Warp,
be sure to read sections 4.8 and 4.9 of this README.
_________________________________________________________
1.2.2 Feature Install Required for Installing Java 1.1.4
OS/2 Feature Install is used to install Java 1.1.4 for OS/2 Warp,
whether you are installing on a local system or on a remote system
using an unattended CID or remote IPL install.
Unattended CID and remote IPL installs of Java 1.1.4 for OS/2 Warp
require version 1.1.1, 1.2, or above of OS/2 Feature Install.
You can obtain the latest version of Feature Install from the
IBM Software Choice web site at:
http://www.software.ibm.com/os/warp/swchoice/
___________________________________________
1.3. HPFS and FAT Partition Considerations
The Runtime and ICAT Debugger components can be installed on a
FAT partition. However, for better performance, install them on
an HPFS partition, which supports long file names. The Toolkit,
Toolkit Documentation, and Samples components must be installed
on an HPFS partition. The Internationalization Support portion
of the Runtime component and the Times New Roman MT 30 Unicode Font
component are installed on the boot partition.
If you use the Guided Install path, all components must reside
on the same partition. Use Advanced Install to select specific
drives and directories for the different components.
Note: If you have only one hard disk with a single FAT
partition, you have three options:
- Leave your system as it is and install only the Runtime
component and, optionally, the ICAT Debugger component.
- Format the FAT partition for HPFS and reinstall all software.
- Purchase a disk partitioning program, such as PartitionMagic.
With sufficient space, PartitionMagic reduces the size of the
current partition (drive C) and creates a new partition
(logical drive D), which can be formatted for HPFS.
_____________________________________________
1.4 Coexistence with Prior Versions of Java
Java 1.1.4 for OS/2 Warp replaces Java 1.1.1 and coexists with
Java 1.0.1 and 1.0.2. OS/2 Warp 4 provides Java 1.0.1. Java
1.0.2 for OS/2 upgraded existing OS/2 Warp 4 systems to a 1.0.2
service level and provides Java 1.0.2 on OS/2 Warp and OS/2 Warp
Server platforms.
___________________________________________
1.4.1 Coexistence with Java 1.0.1 and 1.0.2
The 1.0.x versions of Java are installed in a \JAVAOS2 directory.
The installation program, by default, installs Java 1.1.4 for
OS/2 Warp in a \JAVA11 directory, which allows the two versions of
Java to coexist on the system.
Do not install Java 1.1.4 into the \JAVAOS2 directory. If you
overlay the files in the \JAVAOS2 directory, Java applets
that run in Netscape Navigator for OS/2 no longer work, and
uninstalling Java 1.1.4 for OS/2 Warp leaves the system without
Java support.
Java applications and applets that are run from an OS/2 Command
Prompt or launched from the Desktop use Java 1.1.4 for OS/2 Warp.
The use of Java 1.0.2 for OS/2 outside Netscape Navigator for OS/2
is not supported after Java 1.1.4 for OS/2 Warp has been installed.
_______________________________________
1.4.2 Replacing Java 1.1.1
If Java 1.1.1 is installed on your system, you must either
uninstall it before you install Java 1.1.4 or replace
Java 1.1.1 by installing Java 1.1.4 over (in the same
directory as) Java 1.1.1.
__________________________________________________________
1.5. Backing Up Base OS/2 Files Not Restored on Uninstall
Java 1.1.4 for OS/2 Warp updates base operating system modules as
part of installation of the Runtime component. Uninstalling
Java 1.1.4 for OS/2 Warp 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 appears at the
end of this README in section 5.
_________________________________
1.6. Saving a Copy of CONFIG.SYS
Before installing Java 1.1.4 for OS/2 Warp, save a copy of your
current CONFIG.SYS file. This ensures that you can return to
your original environment if problems occur during installation.
______________________________________
1.7 Minimum Hardware Recommendations
A minimum of 32 MB of random access memory (RAM) provides the best
results when running Java 1.1.4 for OS/2 Warp applications and
applets. Use an Intel(R) 486 processor or better for OS/2 Warp 4
clients. Use an Intel Pentium(R) processor or better for OS/2 Warp
Server systems.
________________________________________________________________
1.8. Installing FixPaks on OS/2 Warp 4 Systems after Java 1.1.4
If you want to install FixPak 2 or greater on an OS/2 Warp 4 system
after you have installed Java 1.1.4 for OS/2 Warp, make sure that
the following files remain as they are before the FixPak is
installed:
CLIFI.EXE
INSTALL.DLL
LIBUNI.DLL
UCONV.DLL
You can do this by using SERVICE.EXE to install the FixPak and
select not to update the files during installation of the FixPak.
As an alternative, you can use another method to install the FixPak.
If you use another method, do one of the following:
- Save the files and then replace them after installing the FixPak.
- Reinstall Feature Install and Java 1.1.4 after installing the
FixPak.
__________________________________________________________________
1.9 Installation Panel Text Missing or Too Long in DBCS Countries
When installing Java 1.1.4 for OS/2 Warp on DBCS versions of OS/2, DBCS
characters might not be displayed on the installation panels or the
lines could exceed the right border of the display window, even when
the window is maximized.
To correct these problems, exit the installation program, open
the Netscape Navigator for OS/2 object, and select the Options
menu item. Open the General Preferences notebook and select the
Fonts tab. Choose the proper encoding for your country and then
set the proportional and fixed fonts to MINCHO. Press OK to save
the changes. When you start the installation of Java 1.1.4 for
OS/2 Warp again, the text should be displayed correctly.
____________________________________________________________________
1.10 Installing on OS/2 Warp 4 Japanese version (without VoiceType)
If you plan to install Japanese FixPak 2 (FX00002) over OS/2
Warp 4 Japanese version (without VoiceType), you should do it
before installing Java 1.1.4 for OS/2 Warp. Otherwise, OS/2 may
not reboot.
If this occurs, see section 4.23 of this README.
__________________________________________________________________
1.11 Japanese Environment Settings on OS/2 Warp 4 Japanese version
Use the following Japanese environment settings for OS/2 Warp 4
Japanese version:
Codepage 932
ShiftJIS code New JIS
_________________________________________________
1.12 Required Fonts on OS/2 Warp Japanese version
To run Java 1.1.4 for OS/2 Warp, the following fonts are required
on your system:
Name Style
------------------------------------------
GOTHIC Normal
GOTHIC HeiseiKakuGothic-W5-H-90-TT
MINCHO HeiseiMincho-W3-H-90-TT
You can check them in the Font Palette, which is in the System Setup
folder in the OS/2 System folder.
GOTHIC Normal font is included in GOTHIC system Japanese font.
GOTHIC HeiseiKakuGothic-W5-H-90-TT is IBM HeiseiKakuGothic
TrueType font with New JIS order.
MINCHO HeiseiMincho-W3-H-90-TT is IBM HeiseiMincho TrueType font
with New JIS order.
These fonts can be installed through the Selective Install program
object, which is in:
- The Install/Remove folder in the System Setup folder on OS/2
Warp 4 systems
- The System Setup folder on OS/2 Warp Server systems.
________________________________________________________________________
2. Installing Java 1.1.4 for OS/2 Warp
The sections that follow tell you how to install Java 1.1.4
for OS/2 Warp on different types of machines.
_______________________________________________________________
2.1. Installing Java 1.1.4 for OS/2 Warp through the Graphical
User Interface (GUI)
To install Java 1.1.4 for OS/2 Warp through the GUI, use
one of the following methods:
______________________
2.1.1. Desktop Method
To install using the INSTALL.EXE object, follow these steps:
1. Open the OS/2 System folder.
2. Open the Drives object.
3. Open the drive where the Java files were extracted.
4. Open the folder where the Java files were extracted.
5. Select the INSTALL.EXE object to start the install program.
The installation program leads you through the installation
steps. A Java 1.1.4 for OS/2 folder is created in the Programs
folder on OS/2 Warp 4 systems and on the Desktop on OS/2 Warp
Server systems.
After the installation is complete, if you want to clean up
the directory in which the Java files were extracted, select
the DELINST.CMD object to remove the Java files and
subdirectories from the directory where they were extracted.
Files and subdirectories not extracted from the Java 1.1.4
package are not erased.
__________________________________
2.1.2. OS/2 Command Prompt Method
To start installation, make sure that you are in the directory
where the Java 1.1.4 for OS/2 Warp files were extracted. At an OS/2
command prompt, enter:
install
The installation program leads you through the installation
steps. A Java 1.1.4 for OS/2 folder is created in the Programs
folder on OS/2 Warp 4 systems and on the Desktop on OS/2 Warp
Server systems.
Optionally, if you want to remove the Java files and
subdirectories from the directory where they were extracted,
make sure that you are in the directory where the Java 1.1.4 for
OS/2 Warp files were extracted. At an OS/2 command prompt, enter:
delinst
Files and subdirectories not extracted from the Java 1.1.4
package are not erased.
_____________________________________________________________
2.1.3. "Files Missing" Warning During Installation
If your Java 1.1.4 installation pops up a warning message
stating that not all the files of a selected component are
present, you might have not extracted the Java 1.1.4 files from
the original ZIP file correctly. Be sure that when extracting
files from the ZIP file, you specify the proper option on your
file extraction utility to create subdirectories. For pkunzip2
this option is -d. If you do not extract the files properly,
you receive warnings about files that already exist while you
are extracting.
_____________________________________________
2.1.4. Recovering from a Failed Installation
If your installation of Java 1.1.4 for OS/2 Warp fails, check
for and delete any remaining install objects. If you do not
delete these install 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 install object consists of a blue box with a
red ribbon and is located on the Desktop for a CID install.
For an attended installation, the object is in the x:\os2\install
folder. To delete the object, select the object with the
right mouse button and choose Delete from the context 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 install object, shut down and restart the system.
___________________________________________________________________
2.1.5. Unable to Create Feature Install Object on OS/2 Warp Server
Systems
If your installation of Java 1.1.4 for OS/2 Warp fails on an OS/2
Warp Server system with a message that the program was unable to
locate or create a Feature Install object, or that it could not
find the response file, shut down and restart the system and run
the installation program again. This problem is being addressed
by OS/2 APAR PJ24851.
__________________________________________
2.2. Unattended (CID) Installation Method
Unattended or CID installations of Java 1.1.4 for OS/2 Warp 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 Java 1.1.4 for OS/2 Warp
response file, JAVA114.RSP, and a secondary response file where
users can override the default selections. The CID.RSP file
is included in the installation package as an example of the
customized response file; this is the only file that needs to be
modified for unattended installations.
Feature Install version 1.1.1 or higher is required for CID
installations. See section 1.2.2 of this README for details.
_____________________________________
2.2.1 Modifying the CID Response File
The CID.RSP response file contains variables that allow you to
select which components to install and the target drive and
directory for each component, where appropriate.
The component names are:
Runtime - Java Runtime
Unicode - Internationalization Support, part of Java Runtime
Environment
Toolkit - Toolkit
TlktDoc - Toolkit Documentation
Samples - Samples
Debugger - OS/2 ICAT Debugger for Java
Unifont - Times New Roman MT 30 Unicode Font
TTengine - Updated TrueType engine, required for the Unicode Font
In the CID.RSP file, set "selection=1" for each component you
want to install, and set "selection=0" for each component you
do not want to install.
Note: There is now a config component associated with
each installable component. The config selection variable
for each component must always be set to the same value as
the selection variable for the component. For example, if
you set toolkit.selection=0, you must also set
toolkitconfig.selection=0.
The Runtime component is always installed in the \JAVA11
directory on the target drive and is a prerequisite for the
Toolkit, Samples, and Debugger components.
The Internationalization Support portion of the Runtime
component and the Times New Roman MT 30 Unicode Font
component are always installed on the boot drive. If the
Times New Roman MT30 Unicode Font component is installed,
the TrueType component is required.
The target drive and directory for the other components can
be specified by setting the drive and path variables to the
desired values. For example, to install the Debugger
component in the F:\JAVADEBUG directory:
debugger.selection=1
debuggerconfig.selection=1
debugger.dbgdrv=F:
debugger.dbgpath=\javadebug
If a previous version of Java exists in the specified
directory on the target drive, the installation program replaces
it. If a previous version of a Java component was installed and
you have not selected to reinstall that component, the installation
program displays a window to warn you that this component will be
downlevel and let you choose to have the component upgraded.
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 doing a
CID installation. The CLIFI command can also be entered as a
single-line command at an OS/2 command prompt as shown below:
clifi /a:c /r2:cid.rsp /r:java114.rsp /b:c: /s:d:\tmp
/l1:ciderr.log /l2:cidhist.log
where:
/r Specifies the fully qualified location of the
Feature Install response file
/b Specifies the boot drive
/s Specifies the fully qualified location of the
extracted Java 1.1.4 for OS/2 Warp files
/l1 and /l2 Specify the fully qualified locations of the
optional log files. Refer to these files, in
addition to the \os2\install\wpinstal.log file
on the boot drive, if problems occur during
installation.
________________________________________
2.2.3 Performing an Unattended Uninstall
To uninstall Java 1.1.4 for OS/2 Warp, enter the following
single-line command at an OS/2 command prompt:
clifi /a:u /f:"<WP_INSTALLED>" /o:INV_JAVA11 /set:Selection=ALL
_____________________________________________
2.3. TME-Architected CID Installation Method
A JAVA114.ADF file is provided for use with Tivoli Management
Environment (TME) architected CID installation products, such as
NetFinity Server and the Tivoli TME-10 Software Distribution
Agent. See the documentation pertaining to the CID installation
product being used for instructions regarding the use of .ADF
files.
When doing a TME-architected CID installation, you must add the
following line to your CID.RSP response file:
java11.CID=TME
Modifying the CID response file is described in section 2.2.1 of
this README.
_______________________________________________________
2.4 NetView DM/2 (NVDM/2) Installation Considerations
A NVDM/2 CID installation requires creating a profile and then
building and cataloging a change file. The NVDM/2 profile
allows you to specify only one response file; however, the
Java 1.1.4 for OS/2 Warp 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 Java 1.1.4 for OS/2 Warp.
Use one of the following methods to install using NVDM/2:
___________________________________________
2.4.1 Put Static Command in NVDM/2 Profile
In the NVDM/2 profile, specify all the CLIFI options in the
PARMS variable. The parameters must be on a single line and
enclosed in double quotation marks:
Program=c:\os2\install\clifi.exe
Parms="/a:c /r2:cid.rsp /r:java114.rsp /b:c: /s:d:\tmp
/l1:ciderr.log /l2:cidhist.log"
This method requires you to modify the profile whenever the
source directory or log file names are changed. You could
replace these values with workstation-specific variable
values, as shown below:
Program=c:\os2\install\clifi.exe
Parms="/a:c /r2:$(ResponseFile) /r:$(SourceDir)\java114.rsp
/b:c: /s:$(SourceDir) /l1:$(LogFile1) /l2:$(LogFile2)"
ResponseFile=$(WorkstatName).rsp
SourceDir=d:\tmp
LogFile1=$(WorkstatName).log
LogFile2=$(WorkstatName).lg2
This second method requires a separate response file for each
workstation and requires WorkstatName to be set appropriately.
_________________________________
2.4.2 Customize JAVA114.RSP File
You can directly modify the JAVA114.RSP file with the
appropriate information. However, because this file is very
large, modifications can be time consuming and error-prone.
If you do decide to modify the file, see Section 2.5.2 of
this README before you begin.
____________________________________________
2.5. Remote IPL Installation Considerations
A remote IPL installation requires creating two response
files and setting up the appropriate directories and files
on the remote IPL server.
Follow these steps for each client to be installed:
1. Place the extracted Java 1.1.4 installation files on the remote
IPL server.
2. Run the GENFIRPL command. (See Section 2.5.1 for information.)
3. Run the CLIFI command for one remote IPL client. (See
Section 2.5.4 for information.)
4. Modify the client FIT file (See Sections 2.5.3 and 2.5.5)
______________________________
2.5.1. Creating Response Files
After placing the extracted Java 1.1.4 for OS/2 Warp 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 JAVA114.RSP for the remote IPL client. The following is a sample
GENFIRPL command. The command should be entered on a single line.
genfirpl /m:c:\javacode /r:c:\ibmlan\rpl
/u:c:\ibmlan\rpluser /f:c:\javacode\java114.rsp
/c:client_name /b:x:
where:
/m Specifies the directory containing the unpacked
Java 1.1.4 for OS/2 Warp installation files on the
remote IPL server
/r Specifies the RPL directory
/u Specifies the RPLUSER directory
/f Specifies the fully qualified name of the response
file for the remote IPL client
/c Specifies the name of the remote IPL client
/b Specifies the remote IPL client's boot drive
/nf Suppresses Java file transfer. Use this flag when installing
additional remote IPL clients, after the first one, to prevent
the Java 1.1.4 files from being installed again for each
new client.
The remote IPL client must not be running when the GENFIRPL
command is issued. One GENFIRPL command must be done for
each remote IPL client, specifying the appropriate client name
and boot drive.
_____________________________________
2.5.2 Modifying the JAVA114.RSP File
The JAVA114.RSP file defaults to installing all the
components of Java 1.1.4 for OS/2 Warp. You can modify this
response file to explicitly set which components you
want to install.
Be sure to use a text editor that handles lines greater than
255 characters, such as TEDIT, to prevent truncation of the
long lines in this file. Because this file is very large,
modifications can be time consuming and error-prone. Make
a backup copy of JAVA114.RSP before modifying it to prevent
loss of data.
The component names that can be selected are:
Runtime - Java Runtime
Unicode - Internationalization Support, part of Java Runtime
Environment
Toolkit - Toolkit
TlktDoc - Toolkit Documentation
Samples - Samples
Debugger - OS/2 ICAT Debugger for Java
Unifont - Times New Roman MT 30 Unicode Font
TTengine - Updated TrueType engine, required for the Unicode Font
Use the selection variables to select the components to install.
The selection variables for the Unifont and TTengine components
must be set to the same value. For example, to install only the
Runtime and Unicode Font components, set the following variables,
which are scattered throughout the JAVA114.RSP file, as shown:
runtime.selection=1
runtimeconfig.selection=1
toolkit.selection=0
toolkitconfig.selection=0
tlktdoc.selection=0
tlktdocconfig.selection=0
samples.selection=0
samplesconfig.selection=0
unifont.selection=1
unifontconfig.selection=1
TTengine.selection=1
TTengineconfig.selection=1
Note: There is now a config component associated with
each installable component. The config selection variable
for each component must always be set to the same value as
the selection variable for the component. For example, if
you set toolkit.selection=0, you must also set
toolkitconfig.selection=0.
_________________________________________
2.5.3 Updating Files for Feature Install
The client_name.FIT file for each remote IPL client must be
modified to include the following, which must be entered on a
single line:
x:\os2\install\install.inv
\\server_name\WRKFILES\client_name\os2\install\install.inv
Substitute the name of the remote IPL server and remote IPL client
for server_name and client_name.
___________________________________________
2.5.4 Starting the Remote IPL Installation
Remote IPL installs 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:\java114.rsp
where /r specifies the fully qualified name of the remote IPL
client's response file, as specified on the GENFICMD
command.
________________________________________________________
2.5.5 Running the Java Samples from a Remote IPL Client
The remote IPL server administrator must add the following lines to
the RPL\FITS\client_name.FIT file to give the remote IPL client the
ability to run the samples provided in the Samples component:
x:\JAVA11\WEBLOGS \\server_name\WRKFILES\client_name\JAVA11\WEBLOGS
x:\JAVA11\HOTJAVA \\server_name\WRKFILES\client_name\JAVA11\HOTJAVA
Substitute the names of the remote IPL server and remote IPL client
for server_name and client_name.
The remote IPL clients can compile the sample code if the samples are
placed in a directory to which the remote IPL client has write access.
_______________________________________________________________________
2.5.6 Upgrading Java 1.1.1 to Java 1.1.4 in the Remote IPL Environment
To upgrade Java 1.1.1 to Java 1.1.4 in the remote IPL environment:
1. Place the extracted Java 1.1.4 installation files on the remote IPL
server.
2. Run the GENFIRPL command. (See Section 2.5.1 for information.)
3. Run the CLIFI command for one remote IPL client. (See Section 2.5.4
for information.
This process updates the Java files on the remote IPL server.
Because all remote IPL clients access the same files on the server,
the upgrade is done for all clients. The client configuration
information is present from the Java 1.1.1 installation.
______________________________
2.5.7 Remote IPL Restrictions
Remote IPL works only on OS/2 Warp 4 clients.
You cannot uninstall Java 1.1.4 for OS/2 Warp in the remote IPL
environment.
________________________________________________________________
2.6. Installing Java 1.1.4 for OS/2 Warp 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 Java 1.1.4 for OS/2 Warp on WorkSpace On-Demand
servers and clients to upgrade from Java 1.1.1.
_________________________________________________________________
2.6.1. Installing Java 1.1.4 for OS/2 Warp for Use on a WorkSpace
On-Demand Server
To install Java 1.1.4 on a WorkSpace On-Demand server, use the
GUI. See Section 2.1 of this README for instructions for using
the GUI to install. During installation on a WorkSpace On-Demand
server, a warning is displayed explaining that you are not updating
Java support for the client. When you select "Yes", installation
proceeds as for other GUI installations.
__________________________________________________________
2.6.2. Installing Java 1.1.4 for OS/2 Warp for a WorkSpace
On-Demand Client
Installation of Java 1.1.4 on a WorkSpace On-Demand Client is done
as an unattended (CID) installation. You can use the instructions
in Section 2.2 of this README and use the CID.CMD and WSOD.RSP
files that are included in the Java 1.1.4 installation package.
_______________________________________________________________
2.6.2.1. Requirements for Installation on a WorkSpace On-Demand
Client
Before you can install Java 1.1.4 for a WorkSpace On-Demand client,
Java 1.1.1 must already be installed. If the Times New Roman MT 30
Unicode Font (the Unifont component) is selected for installation,
it must also have been previously installed with WorkSpace On-Demand.
If this support is not present, the installation completes
without transferring files. In this case, the wpinstal.log shows
that installation completed successfully but it does not show that
any files were transferred.
_________________________________________________
2.6.2.2. Modifying the CID.CMD and WSOD.RSP Files
Before starting the installation, modify the CID.CMD and WSOD.RSP
files as follows:
1. In the CID.CMD file, change /r2:cid.rsp to /r2:wsod.rsp.
2. As described in Section 2.2.2:
- Replace /s:d:\javainst in the CID.CMD file with the drive
and directory where you unzipped the install package.
- Be sure that /b:c in the CID.CMD file points to the boot drive.
3. Verify that the selections in the WSOD.RSP files are
appropriate for what you want to install. The default is to
select the Java Runtime Environment and Unicode Font; all
other components are deselected.
___________________________________________________________
2.6.2.3. Installing Additional Java 1.1.4 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 where Java 1.1.4 is installed for Z.
_________________________________________
2.6.3 Uninstalling on WorkSpace On-Demand
Support for uninstalling Java 1.1.4 requires access to an inventory
object in the Installed Features directory (\os2\install\installed
features). If you install Java 1.1.4 both for the WorkSpace On-Demand
client and for use on the WorkSpace On-Demand server, the Java 1.1.4
inventory object is corrupted or replaced.
To remove Java 1.1.4 from the client space, reinstall the WorkSpace
On-Demand version of Java 1.1.1. This installation will replace
Java 1.1.4.
To remove Java 1.1.4 from the server, delete the \java11 directory
structure. You can delete the directory structure from the Drives
folder in the OS/2 System folder. In addition, if you installed
the Unicode Font, delete the file \os2\dll\tnrmt30.ttf, which is
on the boot drive.
________________________________________
3. Uninstalling Java 1.1.4 for OS/2 Warp
To uninstall Java 1.1.4 for OS/2 Warp, use the Remove Java 1.1.4 for
OS/2 object or the UNINSTAL program. These methods are described
in the sections that follow.
These sections also describe how to optionally restore some OS/2 base
operating system files to their previous versions.
____________________
3.1. Desktop Method
To uninstall using the Remove Java 1.1 object, follow these
steps:
1. Open the OS/2 System folder.
2. Open the System Setup folder.
3. If you are uninstalling on an OS/2 Warp 4 systems only, open
the Install/Remove folder.
4. Open the Uninstall Features folder.
5. Select the Remove Java 1.1.4 for OS/2 Warp object to start the
uninstall program.
6. (Optional) Follow the instructions in section 3.3 to restore
base OS/2 files if they were saved before installing
Java 1.1.4 for OS/2 Warp.
________________________________
3.2. OS/2 Command Prompt Method
To start uninstalling, make sure that you are either in the directory
where the Java 1.1.4 for OS/2 Warp files were extracted or in the
\JAVA11\UNINSTAL directory. At an OS/2 command prompt, enter:
uninstal
The uninstall program leads you through the uninstall process.
Only files and directories created by the install process are
removed. For instance, the HOTJAVA directory created by running
the Applet Viewer is not removed during uninstall.
You can optionally choose to restore base OS/2 files that were
saved before installing Java 1.1.4 for OS/2 Warp by following the
instructions in the next section.
_______________________________
3.3. Restoring Base OS/2 Files
In most cases, the base OS/2 files replaced during the
installation of Java 1.1.4 for OS/2 Warp can be used after you
uninstall Java 1.1.4 for OS/2 Warp. If you made copies of the
original files, as described in section 1.5 of this README, you
can optionally choose to restore them.
Some of the files you backed up are locked during normal system
operation, and cannot be overwritten with the backup copy while
the system is running. To replace these files, follow these
steps:
1. Restart the machine.
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 Java 1.1.4 for OS/2 Warp.
5. At an OS/2 command prompt, enter:
exit
The system now restarts.
______________________________________________________
3.4. State of CONFIG.SYS After Uninstalling Java 1.1.4
If you installed Java 1.1.4 over Java 1.1.1 and you later uninstall
Java 1.1.4, the CONFIG.SYS file is returned to the Java 1.1.1
level.
__________________________
3.5. Unattended Uninstall
For information about performing an unattended uninstall, see
Section 2.2.3 of this README.
_________________________________________
3.6. Uninstalling on WorkSpace On-Demand
For information about uninstalling on WorkSpace On-Demand, see
Section 2.6.3 of this README.
________________________________________________________________________
4. After You Install
_______________________________________
4.1. Additional Sources of Information
The objects in the following list are displayed in the Java 1.1.4
for OS/2 folder only if you are running OS/2 Warp 4. If you are
running OS/2 Warp Server, you can access the associated documents
at the locations shown. (x: is the partition where you installed
Java.)
IBM Centre for Java Technology
http://ncc.hursley.ibm.com/javainfo/hurindex.html
Running Java
x:\JAVA11\runtime.htm
Configure Applet Viewer
x:\JAVA11\cnfgappl.htm
Java Documentation
http://www.javasoft.com/doc.html
Java Developers Kit for OS/2
x:\JAVA11\index.html
Java Toolkit
x:\JAVA11\toolkit.html
Java API
x:\JAVA11\docs\api\API_users_guide.html
OS/2 ICAT Debugger for Java
x:\JAVA11\ICATJAVA\help\icatjava.htm
If you installed the Toolkit, Toolkit Documentation, or OS/2 ICAT
Debugger for Java components in different directories than the
Runtime component, specify the appropriate directory for the last
four objects listed above. The links to the Runtime documentation,
the OS/2 ICAT Debugger for 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 Java 1.1.4 for OS/2 Warp, 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 file and extract
the files again when needed.
_______________________________________________
4.3 Netscape Navigator for OS/2 Considerations
Netscape Navigator for OS/2 runs only Java 1.0.2 applets. Support
for Java 1.1.4 applets may be provided in the future.
___________________
4.4 Class.forName()
Initialization of classes and interfaces is explained in the "Java
Language Specification," Section 12.4.
The section explains that a class is initialized when its static
initializers and initializers for static fields are executed.
Initialization is a distinct phase from class loading.
The following is a quotation from the "Java Language Specification"
by Gosling et. al., Addison-Wesley, Reading, Massachusetts, U.S.A.,
1996:
"12.4 Initialization of Classes and Interfaces
Initialization of a class consists of executing its static
initializers and the initializers for static fields (class
variables) declared in the class. Initialization of an
interface consists of executing the initializers for fields
(constants) declared there. Before a class is initialized,
its superclass must be initialized, but interfaces implemented
by the class need not be initialized. Similarly, the
superinterfaces of an interface need not be initialized
before the interface is initialized.
12.4.1 When Initialization Occurs
A class or interface type T will be initialized at its
first active use, which occurs if:
* T is a class and a method actually declared in T (rather
than inherited from a superclass) is invoked.
* T is a class and a constructor for class T is invoked,
or U is an array with elements type T, and an array of
type U is created.
* A non-constant field declared in t (rather than inherited
from a superclass or superinterface) is used or assigned. A
constant field is one that is (explicitly or implicitly) both
final and static, and that is initialized with the value of a
compile-time constant expression (15.27). Java specifies that
a reference to a constant field must be resolved at compile
time to a copy of the compile-time constant value, so uses of
such a field are never active uses. See 13.4.8 for further
discussion.
All other uses of a type are passive uses."
From this extract it is clear that Class.forName() is not an active
use, so it should not cause static initializers to run.
However, the Sun reference implementations seem to invoke static
initialization upon class loading, so Class.forName() in these
implementations has the side effect of causing class initialization.
This behavior is implicitly assumed in the JDBC examples that use
Class.forName() to load JDBC drivers and expect the JDBC driver to
be immediately usable. The examples are expecting the static
initializers in the JDBC driver to be run by the Class.forName()
so that the static initializer code in the driver can register
itself with the JDBC driver manager.
Because this style of coding is not uncommon, IBM has changed the
behavior of Class.forName in the OS/2 JDK to that of the Sun
reference implementation rather than that of the Sun specification.
Applications can be written to work in either implementation of
Class.forName() by using the following coding style:
Class.forName("myClass").newInstance();
This statement loads the class, returns a class object representing
the new class, and then creates a new object of that class type with
the default constructor. This object is not saved, so it is thrown
away and is removed upon garbage collection.
From Section 12.4 or the "Java Language Specification", it is clear
that if the newInstance() call is successful it must force static
initialization to occur, even when Class.forName() itself does not
cause static initialization.
_______________________________________________
4.5. Disabling the Just-In-Time (JIT) Compiler
A just-in-time (JIT) compiler is provided with Java 1.1.4 for OS/2
Warp. This compiler generates machine code for frequently used
byte code sequences in a Java application or applet on-the-fly
during execution. The JIT is enabled by default.
You can disable the JIT to aid in the isolation of a problem with
a Java application, an applet, or the compiler itself. See the
RUNTIME.HTM file in the x:\JAVA11 directory for details. (x is the
drive on which Java is installed.)
When the JIT compiler is enabled, an uncaught exception generates
a trace back without source line numbers. You must disable the
JIT and run the failing application again to obtain a trace back
with line numbers.
_________________________________________
4.6 Native Methods Need to be Recompiled
Java methods implemented using version 1.0x of Java in a native
language, such as C or C++, need to be recompiled for Java 1.1.4
for OS/2 Warp. See the TOOLKIT.HTML file for details. This file
is in the directory where you installed the Java Toolkit component.
___________________________________________________
4.7 LIBPATH Changes That Could Affect Your System
When the install program determines that OS/2 base DLL modules that
need to be replaced exist in a directory other than x:\OS2\DLL, the
position of x:\OS2\DLL is changed in the LIBPATH to ensure that the
correct version of the modules are loaded.
The IBM Developer's Toolkit for OS/2 Warp is one product that
includes OS/2 base DLL modules in a different directory. This
change does not affect the Toolkit, but could affect other products
that include OS/2 base DLL modules.
____________________________________________________________________
4.8 Applying OS/2 Service after Installing Java 1.1.4 for OS/2 Warp
Java 1.1.4 for OS/2 Warp replaces base operating system modules as part
of installation. When you apply service to your OS/2 system after
installing Java 1.1.4 for OS/2 Warp, you are normally prompted if you
attempt to replace a module that is newer than the one on the
FixPak. However, if you install service by booting from the FixPak
diskettes, you are not prompted when this condition exists,
which could result in one or more modules being regressed. Either
do not apply service by booting from the diskettes, or back up
the base OS/2 modules before installing service and replace them
after applying service.
A complete list of new and changed base modules appears at the end
of this README in section 5.
_____________________________________________________________________
4.9 Installing a FixPak on OS/2 Warp Server Systems after Java 1.1.4
If you install FixPak 30 (or greater) on an OS/2 Warp Server
system after you have installed Java 1.1.4 for OS/2 Warp, and you
want to use the Unicode Font support, you must reinstall the Runtime
and Times New Roman MT 30 Unicode Font components.
_______________________________________________________
4.10 Using 16-Color Mode with Java 1.1.4 for OS/2 Warp
The Java 1.1.4 specification requires 256-color mode (or greater).
Java for OS/2 Warp does not support Java applications and applets
using the Abstract Window Toolkit (AWT) in 16-color mode.
___________________________________
4.11 JDBC-ODBC Bridge Not Provided
Java 1.1.4 for OS/2 Warp provides JDBC (Java Database Connectivity),
a database access interface that provides access to a wide range of
relational databases. However, not all relational databases
provide a JDBC driver. To access databases that support the Open
Database Connectivity (ODBC) standard, a JDBC-ODBC Bridge is
needed. The JDBC-ODBC Bridge allows ODBC drivers to be used as
JDBC drivers by using native code to interface with ODBC. Java
1.1.4 for OS/2 Warp does not provide a JDBC-ODBC bridge.
_______________________________________________
4.12 AWT TextField and TextArea Considerations
The AWT TextField and TextArea controls do not support characters
outside of the current code page. Users running on US English
systems can switch to code page 850 (the multilingual code page, which
supports the Western European languages) to see additional language
characters in these controls.
_________________________________________________
4.13 Controlling Arabic Number Character Display
Users in some countries could unexpectedly see Arabic number
characters appear. Some country-specific versions of OS/2 map the
characters x'00B0' through x'00B9' to the Arabic numbers 0 through
9. To see the desired characters, change the Bidirectional
Attributes in CONFIG.SYS or use the Language page in the
Properties Notebook (Settings Notebook in OS/2 Warp Server) of the
object to obtain the desired effect.
___________________________________________________
4.14 Modifying Font Properties Files Not Supported
Modifying the font properties files provided with Java 1.1.4 for
OS/2 Warp is not supported.
_____________________________
4.15 Printing Considerations
Java provides no mechanism to communicate with the printer driver
to set or retrieve job properties.
Printing from a Java application or applet results in a printer
properties dialog box being displayed. Java 1.1.4 for OS/2 Warp
provides an environment variable called JAVA_NOPRINTDLG that
suppresses the dialog box and prints the file using the default
properties.
To suppress the dialog box and use the default print properties:
SET JAVA_NOPRINTDLG=1
_______________________________________________________
4.16 Behavior of Backslash and Tilde in DBCS Countries
Certain DBCS code pages (for example, 932, 942, 943, 949) do not
have a backslash or tilde character at the same code point as all
other ASCII code pages.
In most ASCII code pages, code point 0x5c is a backslash and code
point 0x7e is a tilde. In code pages 932, 942, and 943, code point
0x5c is a Japanese Yen mark and code point 0x7e is an overline. In
code page 949, code point 0x5c is a Korean Won sign.
The Java compiler, javac, first converts the Java source program
from the local code page to Unicode. It then processes the character
escape sequences, such as \n, by reading the backslash character,
then the 'n' character, and then combining them as a character escape
to generate a Unicode newline, U+000A, before compiling the program.
A problem exists because the backslash character, which is character
0x5C in code page 850, is not in the same position in certain DBCS
code pages. For example, in code page 943, character 0x5C is a Yen
character. If the javac compiler converted code point 0x5c in the
local code page (a Yen mark) in the Java source program to a Unicode
Yen mark (U+00A5), then no backslash characters would be present,
so no character escape sequence processing would be performed.
Furthermore, in code pages 932, 943, and 949, there is no backslash
anywhere in the local code page, so there is no way for a programmer
to generate a Unicode backslash (for use in generating other Unicode
characters using Unicode escape sequences) after code page conversion
in the javac compiler.
To allow programmers to write programs containing a backslash, the
Java virtual machine uses modified code page conversion tables for
code pages 932, 943, and 949. These modified tables pass through
characters 0x00 to 0x7F in the local code page to U+0000 to U+007F
in Unicode. This means that a programmer can use a Yen mark (0x5c)
in code page 932 and 943 and a Won sign (0x5c) in code page 949 to
represent a backslash character (U+005C) in Unicode. An overline
(0x7e) in code pages 932 and 943 can be used to represent a tilde
(U+007E) in Unicode.
These modified codepage conversion tables are also used as the default
for the Java Virtual Machine when running in OS/2 code pages 932, 943,
and 949. These are used for PrintStream, PrintWriter, OutputWriter
and InputReader classes when no explicit character encoding is
specified.
Although using 0x5C in the local code page may be printed as a Yen
mark in the local code page, if an application programmer really
wants a Yen mark, then a Unicode escape should be used to generate
a Unicode character U+00A5. This is needed to make the application
portable to other code pages, and also to cause AWT to display the
correct character glyph. Similar considerations apply if the
programmer wants a real overline: Unicode character U+203E should
be used within the Java program.
Code page 942
Code page 942 has both tilde and backslashes present, though at
different code points from other code pages. Because this code page
does have backslashes and tildes present, even though they are in
different positions from other ASCII code pages, the modified code
page converters are not used by default.
Programs written in this code page can be written using real
backslashes and tilde symbols in the local code page. If programs
written in another ASCII code page where backslash is code point
0x5C need to be compiled then in most cases, the proper behavior
can be achieved by using one of the following methods:
- Replace the 0x5c character in the Java source program with
the backslash character in the local code page (code point
0xfe).
- When compiling the Java application or applet, indicate that
the file is written in a code page different from the local
code page. For example, if the source code was written in
code page 850, use the following command to compile it:
javac -encoding 850 myprogram.java
If the file is written with DBCS characters in code page 942,
using 0x5C to represent the backslash, then the -encoding option
of javac can be used to force the use of character encoding
Cp942c', which passes through characters 0x00 to 0x7F in the
local code page to U+0000 to U+007F in Unicode. For example:
javac -encoding Cp942c myprogram.java
If the source program written in code page 942 using a real
backslash (code point 0xfe) must be compiled on another system,
then use the native2ascii program to convert the Java source
program from the local code page to a basic ASCII code page.
For example:
native2ascii myprogram.java d:\mydest\myprogram.java
To convert from a specific code page to a basic ASCII code page:
native2ascii -encoding 942 myprogram.java d:\mydest\myprogram.java
The file separator character in most ASCII code pages on OS/2 is a
backslash. The file separator character is accessible in a Java
program using the system property 'file.separator' or the static
constant 'java.io.File.separator'.
In code pages 932 and 943, the local file separator character is still
code point 0x5C, but this is displayed at the command prompt as a
Yen mark. Similarly, in code page 949, the separator character is
displayed as a Won sign. The default character converter for these
code pages converts the file.separator character to a backslash in
Unicode, so a Java application sees the file separator as a Unicode
backslash (U+005C).
In code page 942, the local file separator is also a Yen mark, but this
is converted by the Java character converter to a Yen mark in Unicode,
so the Java application sees the file separator character as a
Unicode Yen mark (U+00A5).
Because well-written Java applications always use the file.separator
system property so that they can work on UNIX systems where the file
separator is a forward slash, this should not be a problem. Application
programmers should be sure not to embed path separators in their
programs.
For example, do not use:
FileInputStream x = new FileInputStream("mydir\myfile.ext");
Instead, use:
FileInputStream x = new FileInputStream("mydir" + File.separator+ "myfile.ext");
_________________________________
4.17 Class Name Case Sensitivity
JDK 1.1.4 checks to be sure that the name of a class inside a class
file matches the name of the class the system is attempting to load.
Normally, this is not a problem because the names match. However,
if Java is started from the command line, then the name and case of
the requested class must match the name and case of the class inside
the class file.
For example, if the toolkit is installed, you are in the
x:\java11\demo\hello directory (where x: is the drive where Java
is installed), and you type:
java hello
the response is:
Hello, Warped World!
However, if you type:
java Hello
you receive the error message:
Can't find class Hello or something it requires
Similarly, if you type:
java -verbose Hello
you receive error messages such as:
[Failed to load .\.\Hello.class for this reason: Wrong name]
Can't find class Hello or something it requires
_________________________________________________________________________
4.18 Using Java 1.0.2 for OS/2 After Installing Java 1.1.4 for OS/2 Warp
The use of Java 1.0.2 for OS/2 is not supported from an OS/2 Command
Prompt or the Desktop after you have installed Java 1.1.4 for OS/2 Warp.
You can attempt to run Java 1.0.2 for OS/2 from an OS/2 Command
Prompt by setting the LIBPATH, PATH, and CLASSPATH in the session as
follows:
SET BEGINLIBPATH=x:\JAVAOS2\DLL;
SET PATH=x:\JAVAOS2\BIN;%PATH%
SET CLASSPATH=x:\JAVAOS2\LIB\JEMPCL10.ZIP;.\.
where x: is the drive that contains Java 1.0.2 for OS/2. This
method of running Java 1.0.2 for OS/2 has not been officially
tested and is not supported.
__________________________________________________
4.19 Problems with Time in Java Applets
If you have problems with time in your Java applets, you might need
to set or change the timezone (TZ) variable. To set the TZ
variable, do one of the following:
- Go to the General page in the TCP/IP Configuration notebook.
Set the timezone field, using the online help provided.
- Edit the CONFIG.SYS file and add or change the SET TZ= statement.
__________________________________________________
4.20 Korean OS/2 Users Need PTF for Updated Fonts
If you want to install Java 1.1.4 for OS/2 Warp on a Korean OS/2
system, you must apply PTF PK0817 to your system first. To obtain
the PTF, please 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 Java 1.1.4 for
OS/2 Warp.
__________________________________________________________
4.21 TrueType Fonts Must Be Installed on Chinese Systems
On Simplified or Traditional Chinese systems, ensure that all
available OS/2 TrueType fonts have been installed. To install
these fonts, do the following:
1. Start the Selective Install program by typing
C:\OS2\INSTALL\INSTALL
at an OS/2 command prompt, where C: is the boot drive.
A panel titled "System Configuration" is displayed.
2. Continue to the OS/2 Setup and Installation panel by
clicking on the Next buttons (for Warp 4.0) or the
OK button (for Warp Server 4.0).
3. On the OS/2 Setup and Installation panel, click on the
TrueType Fonts check box.
4. Select the More button to the right of this check box.
5. Make sure all font check boxes are selected. Click OK.
6. Insert the operating system CD (Warp Server 4.0 or Warp 4.0)
into the CD drive.
7. Click OK on the Source Directory panel.
The appropriate fonts are installed. Restart your system
when the font installation completes.
____________________________________________________________
4.22. Conversion between ShiftJIS and Unicode on OS/2 Warp 4
Japanese version
In the Japanese environment, the following conversion tables for
ShiftJIS code (PC code) and Unicode are available:
SJIS
Cp943c
Cp943 = IBM-943
Cp942 = IBM-942
Cp942c
The system default conversion tables are:
- Cp943c for code pages 943 and 932
- Cp942 for code page 942
To use the Cp942 table, set the table name explicitly in a method
or as a parameter. These tables do the following conversions:
For SBCS characters:
PC code Unicode
-------------------------------------------------------------------
SJIS 0x00-0x7F U0000-U007F
Cp942c
Cp943c
Cp942 0x00-0x5B U0000-U005B
Cp943 Yen sign 0x5c U00A5 Yen Sign
0x5D-0x7D U005D-U007D
Overline 0x7E U203E Overline
0x7F U007F
Cent sign 0x80 U00A2 Cent sign
Pound sign 0xA0 U00A3 Pound sterling sign
Not sign 0xFD U00AC Not sign
Backslash 0xFE U005C Backslash
Tilde 0xFF U007E Tilde
For example, in the Cp943c table, the PC code for the range
range 0x00 - 0x7F is converted to Unicode for the range U0000 - U007F
straight. In the Cp942 table, the PC code Yen sign (0x5c) is
converted to the Unicode Yen sign (U00A5).
For DBCS characters:
In the Cp943, Cp943c and SJIS table, the PC code is regarded as the
new JIS order.
In the Cp942 and Cp942c table, the PC code is regarded as the old
JIS order.
For User-Defined Characters and IBM Extended Characters:
In the Cp943 and Cp943c tables, these PC code characters are converted
to Unicode.
In the SJIS table, these PC code characters are NOT converted
to Unicode.
In the Cp942 and Cp942c tables, these PC code characters are converted
to Unicode.
_____________________________________________________________
4.23 Installing Japanese FixPak 2 (FX00002) over OS/2 Warp 4
Japanese version (without VoiceType) and Java 1.1.4
Before you apply the Japanese FixPak 2 after installing Java 1.1.4
for OS/2 Warp 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 band "OS/2" displays 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.
5. Type: exit
The system restarts.
Note: OS/2 Warp 4 Japanese version (with VoiceType) includes
FixPak 2(FX00002).
________________________________________________________________________
5. List of OS/2 Base Modules Changed or Added by Java 1.1.4 for OS/2 Warp
When you install Java 1.1.4 for OS/2 Warp on your system, the following
OS/2 base files are updated, or added if they do not already exist:
\os2\dll\libaux.dll
\os2\dll\libcm.dll
\os2\dll\libcn.dll
\os2\dll\libcs.dll
\os2\dll\libtk.dll
\os2\dll\libuni.dll
\os2\dll\locale.dll
\os2\dll\uconv.dll
\language\codepage\ibm437
\language\codepage\ibm813
\language\codepage\ibm819
\language\codepage\ibm850
\language\codepage\ibm852
\language\codepage\ibm855
\language\codepage\ibm857
\language\codepage\ibm860
\language\codepage\ibm861
\language\codepage\ibm862
\language\codepage\ibm863
\language\codepage\ibm864
\language\codepage\ibm865
\language\codepage\ibm866
\language\codepage\ibm869
\language\codepage\ibm874
\language\codepage\ibm878
\language\codepage\ibm912
\language\codepage\ibm913
\language\codepage\ibm914
\language\codepage\ibm915
\language\codepage\ibm916
\language\codepage\ibm920
\language\codepage\ibm921
\language\codepage\ibm922
\language\codepage\ibm942
\language\codepage\ibm943
\language\codepage\ibm949
\language\codepage\ibm950
\language\codepage\ibm1004
\language\codepage\ibm1089
\language\codepage\ibm1200
\language\codepage\ibm1207
\language\codepage\ibm1208
\language\codepage\ibm1250
\language\codepage\ibm1251
\language\codepage\ibm1252
\language\codepage\ibm1253
\language\codepage\ibm1254
\language\codepage\ibm1255
\language\codepage\ibm1256
\language\codepage\ibm1257
\language\codepage\ibm1275
\language\codepage\ibm1280
\language\codepage\ibm1281
\language\codepage\ibm1282
\language\codepage\ibm1283
\language\codepage\ibm1381
\language\codepage\ibm1386
\language\codepage\os2ugl
\language\codepage\ucstbl.lst
The following file is replaced on OS/2 Warp 4 systems and on
OS/2 Warp Server systems at a FixPak 30 service level or higher:
\os2\dll\truetype.dll
The following file contains Monotype Corporation's Times New Roman
MT 30 TrueType Unicode Font and is installed on OS/2 Warp 4
systems and on OS/2 Warp Server systems at a FixPak 30 level or
higher. If you have previously installed a font with the same
file name, this file replaces it:
\os2\dll\tnrmt30.ttf
________________________________________________________________________
6. TRADEMARKS
The following terms are trademarks of the IBM Corporation in the
United States or other countries or both:
IBM
OS/2
Software Choice
Workplace Shell
Java and HotJava are trademarks of Sun Microsystems, Inc.
PartitionMagic is a trademark of PowerQuest Corporation.
Intel and Pentium are registered trademarks of Intel Corporation
in the United States and other countries.
The Java technology is owned and exclusively licensed by Sun
Microsystems Inc. Java is a trademark of Sun Microsystems Inc.
in the U.S. 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 1997, All rights reserved.
________________________________________________________________________
END-OF-README-FILE
________________________________________________________________________