Contents
Introduction
Thank you for downloading the J2SE™ Development Kit (JDK) 5.0-5 for the OpenVMS I64 Operating System for the Java™ Platform (hereafter called simply the JDK). For 5.0, Sun Microsystems has reverted to the terminology JDK and JRE. These release notes contain installation instructions, new features, known issues, and other information specific to this release of the OpenVMS I64 port of Sun Microsystems' Java™ 2 Platform Standard Edition (J2SE). In addition to these release notes, the release-independent User Guide contains information on getting started using the JDK, using the Plug-in, and troubleshooting. This kit can be used to develop and run Java™ applets and programs on OpenVMS I64 systems, Version 8.2-1 and higher.
The JDK 5.0-5 kit implements the J2SE 5.0 (a.k.a 1.5.0), and is based on Sun's J2SE 1.5.0_20 Solaris Reference Release. It passes all the tests in Sun's Java Compatibility Kit test suite (JCK V1.5a).
Note that the JDK kit contains the HotSpot Virtual Machine that is designed for maximum program execution speed for applications running in a server environment.
To set up up your Java environment, use the following command:
$ @SYS$COMMON:[JAVA$150.COM]JAVA$150_SETUP ! Use the HotSpot VM
Note: The option UsePerfData is set to false by default starting with 5.0-3. This represents a change over the previous release (5.0-2). If you need to use JMX and JMM APIs, please specify -XX:+UsePerfData on the command line when invoking the Java application.
Note: For simplicity, these release notes assume you installed the JDK using the default location and therefore reference SYS$COMMON:[JAVA$150] throughout the text. However, if you specified a destination and installed the kit in that alternate location, substitute that location for the default while reading the examples in this document.
There is always a copy of JAVA$150_SETUP.COM located in the SYS$MANAGER directory. If you are not sure where the JDK was installed, you can always safely use:
@SYS$MANAGER:JAVA$150_SETUP.COM
IMPORTANT: Please make sure you understand the Copyright (copyright.html, installed file) and License (license.html, installed file) information before using this release.
New Features
The following is a list of new features from Sun, in JDK 5.0. HP recommends that you read Sun's Java 2 Platform Standard Edition (J2SE) Documentation for a thorough description of all new features and enhancements available in the J2SE 5.0.
- New language updates: Metadata, Generics, Enumerated types, Autoboxing of primitive types
- New JVM Monitoring and Management API
- Improved out-of-box performance
- New (but compatible) default Java look and feel
Other noteworthy changes include:
- New core XML support including: XML 1.1 with Namespaces, XML Schema, SAX 2.0.2, DOM Level 3 Support and XSLT with a fast XLSTC compiler.
- 32-bit supplementary character support added to the platform as part of the transition to Unicode 4.0 support.
- Java Web Start Improvements
For a complete list of features introduced in 5.0 since the previous major release (1.4), refer to the Summary of New Features and Enhancements on Sun's site.
JDK 5.0-5 New Features
This kit installs JDK 5.0-5, which is a maintenance release with no new features from HP.
JDK 5.0-4 New Features
JDK 5.0-4 is a maintenance release with no new features from HP.
JDK 5.0-3 New Features
JDK 5.0-3 was a maintenance release with no new features from HP.
JDK 5.0-2 New Features
JDK 5.0-2 was a maintenance release with the following new feature from HP:
- Support for user controllable RMS attributes. You can now override the default RMS file operation attributes with attributes of your own choosing. For more information, see Defining RMS Record Attributes.
JDK 5.0-1 New Features
JDK 5.0-1 was the initial release for the OpenVMS I64 Operating System.
Fixed Problems
The following sections provide important information about problems that HP has fixed in JDK 5.0. HP recommends that you also review Sun's Java 2 SDK and Runtime Environment Important Bug Fixes and Changes documentation for information about bug fixes that Sun has made for this release.
Problems Fixed in JDK 5.0-5
JDK 5.0-5 is based on Sun's J2SE 1.5.0_20 Solaris Reference Release and Olson timezone data file tzdata2009g, and passes all the tests in Sun's Java Compatibility Kit test suite (JCK V1.5a). For additional information on the DST changes, please refer to the
Java Technology Software (OpenVMS and Tru64™ UNIX®) website. This JDK is a maintenance release and includes the following fixed problem from HP:
- Previously, incorrect pathname and filename information might have been appended to the name while attempting to rename files. This problem has been fixed.
Problems Fixed in JDK 5.0-4
JDK 5.0-4 is based on Sun's J2SE 1.5.0_17 Solaris Reference Release and Olson timezone data file tzdata2008i, and passes all the tests in Sun's Java Compatibility Kit test suite (JCK V1.5a). For additional information on the DST changes, please refer to the
Java Technology Software (OpenVMS and Tru64™ UNIX®) website. This JDK is a maintenance release and includes the following fixed problem from HP:
- Previously, an application that allocated a large amount of memory in P0 space before starting up the JVM might have experienced an Out-of-memory error. This problem is fixed.
Problems Fixed in JDK 5.0-3
JDK 5.0-3 is based on Sun's J2SE 1.5.0_15 Solaris Reference Release. It includes the following fixed problems from HP:
- A problem with monitoring and management using JMX with the HotSpot VM has been fixed. Previously, users might run into an access violation while starting the VM with the JMX agent enabled.
- Previously, a "%SYSTEM-W-ACCONFLICT, file access conflict" security alarm might have been triggered on application exit if audit alarms for file operation failures were enabled. This defect has been fixed in this release.
- Two problems with the -Xverbosegc option have been fixed in this release. Previously the customer might have seen warning messages or invalid output lines when both
-Xverbosegc and -XX:+UseConcMarkSweepGC were set.
- A problem with JAVA$150_SETUP.COM and JAVA$150_JRE_SETUP.COM has been fixed. Previously, users might have experienced a problem when selecting Fast VM on Itanium, or Hotspot VM on Alpha. The JAVA$150_SETUP.COM and JAVA$150_JRE_SETUP.COM command procedures have been extended so that the FAST and HOTSPOT options are synonymous on both platforms. Specifying either one uses the Fast VM on Alpha, or the Hotspot VM on Itanium.
Java Web Start Technology Usage
Java™ Web Start is an application-deployment technology, which gives you the power to launch full-featured applications with a single click from a web browser. It is located in the jre directory. Some of Java Web Start's features include:
- Runs independently of any browser, so you can shut down your browser or go to another Web page and continue using your application.
- Applications deployed with Java Web Start do not require a browser interface to operate.
- Includes security features of the Java 2 platform.
- The hardware and operating system requirements for using Java Web Start are the same as those recommended for J2SE platform implementation on which it runs.
Java Web Start is included with HP's JDK 5.0-2 and higher on OpenVMS. For information on how to set up and run Java Web Start with JDK 5.0-2 and higher, see 'Using Java Web Start.'
More information, including developer documentation, can be found in Sun Microsystems' documentation at: http://java.sun.com/products/javawebstart/reference/index.html.
Compatibility
JDK 5.0-5 is compatible with previous SDK versions. Most existing programs will run on the 1.5.0 platform. However, some important incompatibilities do exist and are thoroughly discussed in Sun's Java 2 Platform Compatibility with Previous Releases document. For specific J2SE 5.0 incompatibilities refer to the section, Incompatibilities in the Java 2 Platform Standard Edition 5.0 (since 1.4.2).
Installation
The following sections describe how to install the JDK 5.0 kit on your OpenVMS I64 system.
Prerequisites
The prerequisites for running this kit are:
- JDK 5.0 must be installed on an ODS-5 formatted disk.
- OpenVMS I64 V8.2-1 or higher. See Mandatory Patches.
- TCP/IP Services for OpenVMS I64 V5.5 or higher with latest ECO
Note: We do not support MultiNet directly. All of our testing and certification is done using TCP/IP Services for OpenVMS; however, because we do not call UCX directly and use only the socket functions available from HP C, MultiNet should work with this JDK.
- DECWindows Motif V1.5, if you plan on AWT use.
- Secure Web Browser (SWB) 1.7-8
or higher based on Mozilla, or SWB 1.1-12 or higher based on SeaMonkey, if you plan on using Java Plugins with SWB.
-
Kernel support for Thread Manager upcalls must be enabled. Please do not disable Thread Manager upcalls using either the image flags or the MULTITHREAD system parameter.
Mandatory Patches
To successfully install and run the JDK for OpenVMS I64, you must install prerequisite patches for your OpenVMS version (See the list below. Install the patch versions listed, or later, if superseded.). These patches can be downloaded from the IT Resource Center (ITRC) at http://www2.itrc.hp.com/. Note: First-time users must register.
Patches for OpenVMS I64 V8.2-1
- All Rating 1 ECOs (search keyword = 'INSTALL_1' )
- VMS821I_ACRTL-V0400 (or latest ECO)
- VMS821I_PTHREAD-V0300 (or latest ECO)
- VMS821I_WEBL-V0100 (or latest ECO)
- HP-I64VMS-TCPIP-V0506-9ECO3-1 (or latest ECO)
Patches for OpenVMS I64 V8.3
- All Rating 1 ECOs (search keyword = 'INSTALL_1' )
- VMS83I_ACRTL-V0700 (or latest ECO)
- VMS83I_PTHREAD-V0100 (or latest ECO)
- TCPIP-V0506-9ECO3-1 (or latest ECO)
Patches for OpenVMS I64 V8.3-1H1
- All Rating 1 ECOs (search keyword = 'INSTALL_1' )
- VMS831H1I_ACRTL-V0300 (or latest ECO)
- TCPIP-V0506-9ECO3-1 (or latest ECO)
Note for ECOs:
Because the status of ECOs changes frequently as new versions supersede previous versions, we recommend that you search the ECOs cited above, and install the 'most recent' version resulting in your search. To verify that you have the correct file, refer to the 'Patch Details'.
For more information, refer to the patch installation page on the Web site.
Installing the Kit
To install the JDK kit:
- Download and install the prerequisite ECOs.
- Download the file
HP-I64VMS-JAVA150-V0105-5-1.PCSI_SFX_I64EXE (~562,000 blocks) from our Software Download web page and run the file to extract it into 2 files:
$ RUN HP-I64VMS-JAVA150-V0105-5-1.PCSI_SFX_I64EXE
HP-I64VMS-JAVA150-V0105-5-1.PCSI$COMPRESSED (~752,000 blocks)
HP-I64VMS-JAVA150-V0105-5-1.PCSI$COMPRESSED_ESW (18 blocks)
Important: If you move the above files, make sure that they remain together in the same directory.
Note: If you are downloading the file to an ODS-5 disk, the unpacking operation might convert the filenames into lower case. Convert them to upper case before proceeding; for example:
$ RENAME hp-i64vms-java150-v0105-5-1.pcsi$compressed -
HP-I64VMS-JAVA150-V0105-5-1.PCSI$COMPRESSED
Note: You can download the file and expand to .PCSI$COMPRESSED wherever you like; however, the installation (Product Install) must be done onto an ODS-5 formatted disk.
- To extract a local copy of these Release Notes before installing the JDK:
$ PRODUCT EXTRACT FILE JAVA150 -
/SOURCE=[directory_where_you_put_the_PCSI$COMPRESSED_file] -
/SELECT=RELEASE_NOTES.HTML -
/DEST=[]
- Install the JDK kit from the
.PCSI$COMPRESSED file obtained, using the PCSI (POLYCENTER Software Installation) utility PRODUCT command:
$ PRODUCT INSTALL JAVA150 -
/SOURCE=[directory_where_you_put_the_PCSI$COMPRESSED_file] -
/NORECOVERY_MODE
By default, the JDK gets installed in root directory SYS$COMMON:[JAVA$150]. As an alternative to installing the kit in the default location SYS$COMMON:[JAVA$150], you can specify /DESTINATION=device-name:[directory-name] on the PRODUCT command line, and the kit will be installed at that specified location.
Remember: JDK 5.0 must be installed onto an ODS-5 formatted disk.
Also, the following files are installed by the PCSI utility with a file attribute of ARCHIVE:
SYS$COMMON:[JAVA$150.COM]JAVA$150_SETUP.COM
If a file having any of these names already exists on the system, the installation process renames it to a new name with a file type ending in _OLD, before loading the new copy from the kit. Only the latest version of the existing file is preserved (by being renamed to file.type_old) before PCSI deletes all remaining versions.
For example, an existing SYS$COMMON:[JAVA$150.COM]JAVA$150_SETUP.COM is renamed to SYS$COMMON:[JAVA$150.COM]JAVA$150_SETUP.COM_OLD before the new copy is copied from the kit.
If you have previously personalized any of these files, you might need to merge your personalizations with the new copies.
Notes:
- The PCSI PRODUCT tool for OpenVMS I64 installs different versions of the JDK using unique product names. For example:
- SDK v 1.4.2-n is installed as product
JAVA142
- JDK 5.0-n is installed as product
JAVA150
Therefore, if you decide to update to an earlier or later version of the JDK within the same product, you should not use the PCSI PRODUCT REMOVE command. Instead, use the PRODUCT INSTALL of the desired kit. By following these instructions you avoid potential shared-file conflicts.
- Installing in the
SYS$COMMON area requires privileges. The SYS$COMMON:[JAVA$150] directory is the typical location for the installation of this kit.
- To use JDK 5.0, you must first set up the Java environment.
Because you can have multiple JDK versions installed on your OpenVMS system, and because you can change from one version to the other, you need to follow specific steps to set up your Java environment properly. To run the command procedure to do this, refer to Setting Up the Java Environment in the User Guide.
- Refer to the User Guide for additional information on how to use this product in an OpenVMS environment. Local copies of these Release Notes and User Guide are installed at
SYS$COMMON:[JAVA$150.DOCS]RELEASE_NOTES.HTML and SYS$COMMON:[JAVA$150.DOCS]USER_GUIDE.HTML, respectively.
Determining Your Installed Version
After downloading, installing, and running the command procedure to set up the Java environment, use the java -fullversion command to display the version. For example:
$ java -fullversion
java full version "1.5.0-n"
where n identifies the specific JDK 5.0 that is installed.
To switch from one version to another, see Switching Versions in the User Guide.
Contents of the JDK
This section provides a general summary of the files and directories contained in the JDK once it has been installed on your system.
Note: For simplicity, these release notes assume you installed the JDK using the default location and therefore reference SYS$COMMON:[JAVA$150] throughout the text. However, if you specified a destination and installed the kit in that alternate location, substitute that location for the default while reading the examples in this document.
Development Tools
In SYS$COMMON:[JAVA$150.BIN]
This area contains programs that will help you develop, execute, debug, and document programs written in the Java programming language. For further information, see Sun's Tools and Utilities page.
Important: Review the information in the Interpreting Commands and OpenVMS Operating System Differences table in the User Guide to understand fully the nuances and differences in JDK 5.0 on OpenVMS I64.
Runtime Environment (JRE)
In SYS$COMMON:[JAVA$150.JRE]
An implementation of the Runtime Environment (JRE) for use by the JDK. The runtime environment includes a virtual machine for Java 2, class libraries, and other files that support the execution of programs written in the Java programming language. (Note: The JRE included in the JDK is separate from the JRE kit).
Additional Libraries
In SYS$COMMON:[JAVA$150.LIB]
Additional class libraries and support files required by the development tools.
Demo Applets and Applications
In SYS$COMMON:[JAVA$150.DEMO]
Examples, with source code, of programming for the Java platform. These include examples that use Swing and other Java Foundation Classes.
Additional Demos
In SYS$COMMON:[JAVA$150.VMS_DEMO]
Examples that demonstrate what is needed to write native C programs to interact with Java code.
C Header Files
In SYS$COMMON:[JAVA$150.INCLUDE]
Header files that support native-code programming using the Java Native Interface and the Java Virtual Machine Debug Interface, as described on the Sun site.
Source Code
In SYS$COMMON:[JAVA$150]SRC.ZIP
Java programming language source files for all classes that make up the Java 2 core API (that is, source files for the java.*, javax.* and org.omg.* packages, but not for com.sun.* packages). This source code is provided for informational purposes only, to help developers learn and use the Java programming language. These files do not include platform-specific implementation code and cannot be used to rebuild the class libraries. To extract these files, use this command:
$ jar xvf src.zip
Do not modify core API source files. To extend the behavior of the core API, write subclasses of the core API classes.
Using System.getenv
Similar to predefining environment variables for a process on UNIX systems, you can define a list of environment variables to be available to an OpenVMS Java application. With JDK 5.0-4 and higher, you can use System.getenv to build a list of environment variables.
For security reasons, we have not implemented a blind default list of environment variables. Also, we suggest keeping the variable lists to only those used by your Java application. For example, exporting the logical that points to the location of SYSUAF in a web application might be seen as a security issue because normal Web application users are not required to actually log in to the system.
By default, System.getenv builds a list of environment variables from the following four logicals:
JAVA$GETENV_PROCESS_LIST
JAVA$GETENV_JOB_LIST
JAVA$GETENV_GROUP_LIST
JAVA$GETENV_SYSTEM_LIST
The following logicals are also included in the list:
HOME
USER
TERM
PATH
Rules for each item found in the list:
- Search the default logical name tables (lnm$file_dev):
- If found, build a colon separated list.
- If any value appears to be in OpenVMS file format, convert the name to UNIX format following the Java$filename_controls rules.
- If the logical is not found, Java checks for a symbol definition:
Symbols are translated “as is”. OpenVMS file format is not converted.
- If either a logical or symbol is not found, the item is not included in the list.
Note: String System.getenv(String) is case-sensitive. Because Java for OpenVMS attempts to follow UNIX behavior, this lookup is designed to be case-sensitive. This means you must define the item in the list exactly how you would on a UNIX system. Keeping the case-sensitive property also supports the usage of the various DECC Run-Time Library (RTL) logicals that enable or disable case.
To match a true UNIX environment, define the following DECC RTL logicals as TRUE:
DECC$EFS_CASE_PRESERVE TRUE
DECC$EFS_CHARSET TRUE
And define the following DECC RTL logical as FALSE, or leave it undefined:
DECC$EFS_CASE_SPECIAL FALSE (or not defined)
If DECC$EFS_CASE_PRESERVE and
DECC$EFS_CHARSET are not defined, or are defined as FALSE, all items in the list will be lowercased.
If DECC$EFS_CASE_SPECIAL is defined as TRUE, all items that contain all uppercase letters will appear lowercased in the list.
For example:
$ define JAVA$GETENV_SYSTEM_LIST SYS$LOGIN, SYS$SCRATCH, SYS$DISK
$ define JAVA$GETENV_PROCESS_LIST foobar, testing, ZTEST ! ZTEST must be all caps
$ foobar == "symbol value"
$ define testing "logical value"
$ def ZTEST "ZTESTFOUND"
System.getenv should return a string list like the following:
foobar=>symbol value
XFILESEARCHPATH=>/usr/dt/app-defaults/%L/Dt
sys$scratch=>/SYS$SYSROOT/sysmgr
ZTEST=>ZTESTFOUND
NLSPATH=>/usr/dt/lib/nls/msg/%L/%N.cat
USER=>SYSTEM testing=>logical value
sys$disk=>/SYS$SYSROOT/sysmgr
sys$login=>/SYS$SYSROOT/sysmgr
HOME=>SYS$SYSROOT:[SYSMGR]
TERM=>unknown
PATH=>SYS$SYSROOT:[SYSMGR]
Resolving Domain Names in Java
Domain-name resolving can be done by the sockets API or the JDK itself. To make domain-name resolving work in the JDK on OpenVMS systems, you must configure your system as follows:
- Configure the BIND resolver using the ASCII configuration file TCPIP$ETC:RESOLV.CONF. For more information, refer to the document HP TCP/IP Services for OpenVMS Management.
- Add the directory map into the
java$filename_controls logical:
$ show log java$filename_controls
"JAVA$FILENAME_CONTROLS" = "131592" (LNM$JOB_899A9900)
If the directory mapping bit is not set as in the above example, set it as follows:
$ b=131592+536870912 ! add in the directory mapping bit
$ show sym b
B = 537002504 Hex = 20020208 Octal = 04000401010
$ def java$filename_controls 537002504
- Direct java to get the DNS configuration from
/sys$system/resolv.conf instead of /etc/resolv.conf:
$ DEF JAVA$DIRECTORY_MAPPING_COUNT 1
$ DEF JAVA$DIRECTORY_MAPPING_01 "/etc/resolv.conf=/sys$system/resolv.conf"
Using Java Web Start
Java Web Start provides the ability to run Java applications with a single click from your Web browser. If the application is not on your system, Java Web Start will download all needed files to run the application. It caches these files on your system so that the application can be rerun without having to once again download the application.
In most cases, Java Web Start for OpenVMS works as described in Sun’s Java Web Start documentation. However, some OpenVMS specific setup tasks must be done before running Java Web Start applications from the HP Secure Web Browser for OpenVMS I64 (based on Mozilla)
These setup tasks are:
- Install JDK 5.0-2 or higher.
- Download and install the HP Secure Web Browser for OpenVMS I64 (based on Mozilla).
- Define a helper application for jnlp files in Mozilla by doing the following:
Run Mozilla interactively.
When Mozilla comes up, click on “Preferences…” in Mozilla’s “Edit” menu.
Click on “Helper Applications.”
Click on “New Type.”
Enter the following information:
| Mime Type: |
application/x-java-jnlp-file |
| Description: |
Java Web Start |
| Extension: |
jnlp |
| Open it with: |
/sys$manager/java$150_javaws.com |
Then, press “OK.”
To run Java Web Start as a standalone application, install JDK 5.0-2 or higher. Then enter the commands:
$ @SYS$COMMON:[JAVA$150.COM]JAVA$150_SETUP.COM
$ define DECC$EFS_CASE_PRESERVE ENABLE
$ javaws
Setting DECC$EFS_CASE_PRESERVE will enhance Java Web Start’s ability to find cached applications on your system.
Defining RMS Record Attributes
JDK 5.0-2 and higher provides the capability to exercise closer control over Record Management Services (RMS) file attributes used by the CRTL library to manipulate files on behalf of the J2SDK. You can now override the default RMS file operation attributes with attributes of your own choosing.
This is done by defining the OpenVMS logical name JAVA$FILENAME_MATCH_LIST. The value of JAVA$FILENAME_MATCH_LIST consists of file name patterns and RMS attributes. The RMS attributes are passed to the CRTL library by the J2SDK when it asks the CRTL library to manipulate files whose names match the file name patterns.
The value consists of one or more comma separated specifiers, where each specifier is of the form:
"file_match_pattern=<RMS parameter>/<additional RMS parameter>/<..."
Restrictions:
- Patterns/RMS parameters can not contain the ':' character.
- JRE file sharing will NOT be enabled for files matching the file_match_pattern.
- Other Java logical name settings (e.g. JAVA$CREATE_STMLF) may be ignored.
Examples:
$ define JAVA$FILENAME_MATCH_LIST "*.obj=ctx=stm"
This causes the attribute "ctx=stm" to be used when the CRTL library opens a file whose name matches the pattern “*.obj”.
Possible Usage:
On OpenVMS Alpha, *.obj files have variable length record format with a two byte header. By default, the J2SDK relies on the CRTL library to treat all files as if they have Stream_LF record format. This causes problems when using the jar tool to create a .jar file composed of .obj files. As the CRTL library reads the .obj files it converts their records to Stream_LF record format by removing the 2 byte variable length header and adding a <LF> character to the end of each record. When the .obj files are extracted from the .jar file their two byte record header will have been lost and tools such as the OpenVMS linker will not be able to properly read these .obj files.
You can avoid this problem by setting JAVA$FILENAME_MATCH_LIST as specified above. This will cause the jar tool to copy the .obj files into the .jar file without losing their two byte record headers. When the .obj files are restored they can then be converted back to a format that is acceptable to the OpenVMS linker by using the OpenVMS “$ set file/attr=(RFM:VAR)” command.
$ define JAVA$FILENAME_MATCH_LIST "*.*=shr=get,put,upi/rop=rea"
This is the equivalent of:
$ define java$file_open_mode 3
However, without JRE file sharing.
$ define JAVA$FILENAME_MATCH_LIST "*.exe=ctx=stm", -
"*.pcsi_sfx_axpexe=shr=get,put,upi/rop=rea", -
"/apache$root/logs/error*=shr=get,put,upi/rop=rea/fop=dfw,sup/mbc=127"
This example demonstrates combining multiple settings using a single instance of JAVA$FILENAME_MATCH_LIST.
This setting causes:
- *.exe files to be treated as Stream_LF record format.
- *.pcsi_sfx_axpexe files to be opened as shared.
- /apache$root/logs/error* files to be opened as shared, with deferred write, and allocated a larger than normal Multiblock Count (mbc)
For a complete list of the RMS attributes that can be set via this mechanism, see:
http://h71000.www7.hp.com/DOC/83final/5763/5763pro_027.html#fab_rab_keywords_1.
Known Issues
This section provides descriptions of the known issues and limitations that exist in JDK 5.0 for OpenVMS I64; these issues include the following:
-
The “s” mode of the RandomAccessFile class does not function as expected: it is ignored by the JDK. It requires a fix in the C runtime library that will be available in a future version of OpenVMS.
- -Xeprof option: Generates profile data for HPjmeter is not supported.
- Java Networking IPv6 support is not included in this JDK release.
- Java will not run properly if the logical name DECC$DISABLE_TO_VMS_LOGNAME_TRANSLATION or DECC$FILENAME_UNIX_ONLY is defined. Running Java with these logical names set is not supported.
Note: Java may not run properly with other DECC$* logical names defined.
- The jinfo, jmap, jsadebugd, and jstack troubleshooting tools, introduced in JDK 5.0, are not supported on OpenVMS I64.
- The command line option -XX:+UseParallelOldGC is not supported in this release.
- In order to support Japanese fonts you need to be using the Motif Toolkit instead of the default XToolkit. To use the MToolkit there are three logicals you need to re-define:
$ define JAVA$MAWT_SHR -
SYS$COMMON:[JAVA$150.JRE.LIB.IA64.MOTIF12]JAVA$MAWT_SHR.EXE;
$ define JAVA$MAWT_G_SHR -
SYS$COMMON:[JAVA$150.JRE.LIB.IA64.MOTIF12]JAVA$MAWT_G_SHR.EXE;
$ define AWT_TOOLKIT "MToolkit"
Note: the last one was not previously defined in SETUP.COM.
To switch back to using the XToolkit, just redefine the first two logicals back to their original values, and either de-assign the AWT_TOOLKIT logical or define it to be "XToolkit".
Important: Review the information in the Interpreting Commands and OpenVMS Operating System Differences table in the User Guide and the remaining sections to fully understand the nuances and differences in this JDK.
Documentation
The JDK 5.0 documentation tree begins at the following location on the system where the JDK is installed:
SYS$COMMON:[JAVA$150.DOCS]INDEX.HTML
The installed documentation is in HTML format and includes this release notes file and the user guide file, as well as the aforementioned index.html file.
Note: For simplicity, these release notes assume you installed the JDK using the default location and therefore reference SYS$COMMON:[JAVA$150] throughout the text. However, if you specified a destination and installed the kit in that alternate location, substitute that location for the default while reading the examples in this document.
For core API documentation, refer to the following sources:
Also, you can browse the Software Documentation page on our web site. Optimizing Java Technology Software Performance on OpenVMS provides tips on improving Java performance on OpenVMS systems.
For more information on this release, refer to the Release Notes for the J2SE 5.0 software from Sun Microsystems, and to our User Guide for this JDK.
If you are new to the Java programming language, you can browse or download Sun's Java Tutorial.
Problem Reporting
To report problems, refer to our Software Support web page.
|
