Readme
Compaq Run Time Environment (RTE) v 1.3.1-3
for the OpenVMS Operating System
for the Java™ Platform

Introduction
Installing the RTE
Using the Run Time Environment
Using the Plug-in
- Installing and Running Mozilla 0.9.6 and the Plug-In
- The Plug-in Control Panel
Redistributing the RTE
Bundling the RTE

Introduction

Thank you for downloading Compaq Run Time Environment (RTE) v 1.3.1-3 for the OpenVMS Operating System for the Java™ Platform (hereafter called the Compaq RTE or, simply, the RTE). The RTE comprises the Java virtual machine, the Java platform core classes, and supporting files. It is the runtime part of Compaq Software Development Kit (SDK) v 1.3.1 for the OpenVMS Operating System (hereafter called the Compaq SDK or the SDK), but without the development tools such as compilers and debuggers. The RTE contains Compaq Plug-in software that enables Mozilla® (minimum version 0.9.6) to use the RTE to run Java applets. This Readme provides installation instructions for the RTE and information that may be useful for developers who want to redistribute the RTE with their software. Also, note that Compaq Fast Virtual Machine (Fast VM) is now included with the RTE kit, but is not the default VM. After installing the RTE, you can select either the classic VM or Compaq Fast VM as your virtual machine. For more information about this release, refer to the SDK v 1.3.1-3 Release Notes.

IMPORTANT: Please make sure you understand the Copyright (COPYRIGHT.TXT, installed file) and License (LICENSE.TXT, installed file) information before using this release. On OpenVMS the Java virtual machine has a minimum required value for PGFLQUOTA of 196608 blocks (96 MB). Please see the Setting Process Quotas for Better Performance on OpenVMS section of the Compaq SDK Release Notes for more information.

Installing the RTE

To install and use this kit on OpenVMS systems, you must first download and install the operating system patches as described in the SDK v 1.3.1 OpenVMS Patch Installation page.

Compaq suggests that the RTE be installed in its own subdirectory (referred in Figure 1 as <JRE_RUNTIME_BASE>). This allows you to update the RTE independently of updates to your application, and vice versa.

Figure 1: Sample RTE Installation

    
              <APP-DIR>
                  |
 +---------+------+---------------------+
 |         |                            |
BIN       LIB                   <JRE_RUNTIME_BASE>
 |         |                            |
     APPLICATION.JAR         +----------+--------+-------+
                             |          |        |       |       
                            BIN        LIB    PLUGIN    DOC

                                   Supplied by Compaq

The files that make up the RTE are bundled into two OpenVMS BACKUP save sets:

JRE-V131-3.A
JRE-V131-3.A is a REQUIRED subset of files (approximately 55,000 blocks). Your licensing agreement requires that if you redistribute any part of the RTE, you must redistribute this set of files in its entirety. If you do not distribute all files, the RTE and your application may not work. To obtain a detailed list of the files in this save set, use the following command:
  $ BACKUP/LIST JRE-V131-3.A/SAVE_SET
Note: The Compaq Fast VM files are included in this save set.

JRE-V131-3.B
The second save set, JRE-V131-3.B is an OPTIONAL subset of files (approximately 7,500 blocks). You may need some of these files to fully support your application in an international arena. This set does not need to be deployed in its entirety. Table 1 provides detailed list of the files in this save set.

To download and unpack the REQUIRED and OPTIONAL save sets, do the following:

Download:
Download DEC-AXPVMS-JRE-V0103-13-1.SAV_SFX_AXPEXE (approximately 32,000 blocks) from our web site. Execute this file to create the JRE-V131-3.A and JRE-V131-3.B save sets:
```
$ RUN DEC-AXPVMS-JRE-V0103-13-1.SAV_SFX_AXPEXE
```
Unpack Save Sets:
Unpack the JRE-V131-3.A and JRE-V131-3.B files into the appropriate subdirectories of your application. Continuing with the typical directory structure illlustrated in Figure 1, move the save sets into the [.JRE_RUNTIME_BASE] directory, then issue the following commands (edited to match your actual disk and directory names):
```
$! Position yourself to the base directory for the RTE components

$ SET DEFAULT USER1$:[APP-DIR.JRE_RUNTIME_BASE]
$!
$! To unpack the JRE-V131-3.A save set,
$ BACKUP JRE-V131-3.A/SAVE [...]*.*
$!
$! To optionally unpack the JRE-V131-3.B save set,
$ BACKUP JRE-V131-3.B/SAVE [...]*.*
```

For information on bundling the RTE with application software for redistribution, refer to Bundling the RTE.

Table 1 lists the files in the optional save set, JRE-V131-3.B:

Table 1: Files in the Optional Save Set

File	Contents
[BIN]JAVA$KEYTOOL.EXE
[BIN]JAVA$POLICYTOOL.EXE
[BIN]JAVA$RMID.EXE
[BIN]JAVA$RMIREGISTRY.EXE
[BIN]JAVA$TNAMESERV.EXE
[BIN]KEYTOOL.
[BIN]POLICYTOOL.
[BIN]RMID.
[BIN]RMIREGISTRY.
[BIN]TNAMESERV.
[LIB]FONT_PROPERTIES.AR	AWT font properties for Arabic locale
[LIB]FONT_PROPERTIES.EXCURSION	AWT font properties for Excursion
[LIB]FONT_PROPERTIES.IW	AWT font properties for Hebrew locale
[LIB]FONT_PROPERTIES.JA	AWT font properties for Japanese locale
[LIB]FONT_PROPERTIES.KO	AWT font properties for Korean locale
[LIB]FONT_PROPERTIES.TH	AWT font properties for 8859-2 locale
[LIB]FONT_PROPERTIES.ZH_EUC_CN	AWT font properties for Chinese locale
[LIB]FONT_PROPERTIES.ZH_HK_BIG5	AWT font properties for Chinese locale
[LIB]FONT_PROPERTIES.ZH_HK_EUC_TW	AWT font properties for Chinese locale
[LIB]FONT_PROPERTIES.ZH_TW_BIG5	AWT font properties for Chinese locale
[LIB]FONT_PROPERTIES.ZH_TW_EUC_TW	AWT font properties for Chinese locale
[LIB]I18N.JAR	I18N character conversion classes from sun.io
[LIB]PSFONT_PROPERTIES.JA	Japanese Postscript® printer property file
[LIB]PSFONTJ2D.PROPERTIES	Postscript® printer property file for Java 2D printing

Using the Run Time Environment

After installing the RTE, a number of symbols and logicals need to be set up to enable you to use the RTE. An RTE setup command file, JAVA$131_JRE_SETUP.COM, is deposited into the [.LIB] directory, resulting from restoring JRE-V131-3.A. You can select either the classic VM or Fast VM as your virtual machine using this command file. Run this command file as follows:

$ @USER1$:[APP-DIR.JRE_RUNTIME_BASE.LIB]JAVA$131_JRE_SETUP [FAST]

where USER1$:[APP-DIR.JRE_RUNTIME_BASE. denotes the actual disk and directory name where you installed the RTE. Use the parameter FAST to specify Fast VM; otherwise, the classic VM will be used.

The Java command-line tool can then be used to launch your Java application using the RTE.

Using the Plug-in

Compaq Plug-in v 1.3.1 enables users to run Java applets and JavaBeans™ components on web pages using the RTE as an alternative to using the default virtual machine for Java 2 that comes with the web browser. It is based on Java Plug-in 1.3.1 provided by Sun Microsystems and contains similar functionality.

For additional information on topics such as Java Plug-in Security, using signed applets, JNI and Java Plug-in, Using Java Plug-in in Intranet Environments, and How Proxy Configuration Works in Java Plug-in, see the Sun Microsystems Java Plug-in 1.3 Documentation web page; the documentation is the same for the Java Plug-in 1.3.1.

Note: You must be running Mozilla® 0.9.6 or higher.

Installing and Running Mozilla 0.9.6 and the Plug-in

To install Mozilla 0.9.6:

Download Mozilla from http://mozilla.org/releases.
Refer to Mozilla Technology Demonstration Release for OpenVMS Alpha Installation Guide and Release Notes to install Mozilla on your system.

To run Mozilla:

$ @sys$common:[mozilla]mozilla

Note: We strongly recommend that you run Mozilla as an interactive job as indicated above.
If you spawn it off as a subprocess

$ spawn/nowait @sys$common:[mozilla]mozilla

you will likely exhaust some resources if you attempt to use the plug-ins for anything non-trivial.

To enable the Compaq RTE within your browser:

Set preference:
Edit->Preferences
Click on Advanced.
Check button labeled Enable Java.
Exit Mozilla.
When both RTE v 1.3.1 and Mozilla 0.9.6 have been installed, perform a one-time file copy to install the Plug-in:

$ copy /prot=W:RE USER1$:[APP-DIR.JRE_RUNTIME_BASE.PLUGIN.ALPHA.NS600]LIBJAVAPLUGIN_OJI.SO SYS$COMMON:[MOZILLA.PLUGINS] Thereafter, you can set up for Java operation:

$ @USER1$:[APP-DIR.JRE_RUNTIME_BASE.LIB]JAVA$131_JRE_SETUP.COM where USER1$:[APP-DIR.JRE_RUNTIME_BASE. denotes the actual disk and directory name where you installed the RTE.
Then run Mozilla:

$ @sys$common:[mozilla]mozilla

Mozilla will notice that new plug-ins are available and will then initialize those plug-ins for the current invocation.

To verify that Mozilla has found the plug-ins refer to:

Help->About Plug-ins

Mozilla will display the plug-ins it has initialized.

The Plug-in Control Panel

A Plug-in Control Panel lets you change Plug-in options such as proxies and enabling of the Java console window. It also allows you to switch the RTE version you want to run with your Plug-in. To run the Control Panel, enter the following command:

$ ControlPanel

Or you can use the Mozilla browser to visit the Control Panel applet page that was installed as

USER1$:[APP-DIR.JRE_RUNTIME_BASE.DOC]ControlPanel.html

where USER1$:[APP-DIR.JRE_RUNTIME_BASE. denotes the actual disk and directory name where you installed the RTE. For example:

@sys$common:[mozilla]mozilla - file:///USER1$/APP-DIR/JRE_RUNTIME_BASE/DOC/ControlPanel.html

where USER1$/APP-DIR/JRE_RUNTIME_BASE denotes your actual disk and directory name where you installed the RTE.

Refer to Sun's Java Plug-In Control Panel web page for information about additional features and uses of the Java Plug-in Control Panel.

Redistributing the RTE

If you redistribute the RTE, you must follow the terms of the RTE Binary Code License agreement, which includes these terms:

Do not arbitrarily subset the RTE. You may omit only the files in the JRE-V131-3.B optional subset.

Include in your product's license the provisions called out in the RTE Binary Code License.

The following SDK files may be redistributed with the RTE:

SYS$COMMON:[JAVA$131.BIN]JAVAC.
SYS$COMMON:[JAVA$131.BIN]JAVA$JAVAC.EXE
SYS$COMMON:[JAVA$131.LIB]TOOLS.JAR

These files include Java 2 SDK tools classes, including the classes for the javac compiler.

Bundling the RTE

For your end users to run your software, they'll need a Java runtime environment installed on their systems. The SDK contains a runtime environment, of course, so your customers could use that if they happen to have it installed. However, a better bet for most of your end users will be the RTE, for several reasons:

The RTE is redistributable, unlike the SDK. The RTE Binary Code License agreement allows you to package it with your software. By distributing the RTE with your application, you can ensure that your customers will have the correct version of the runtime environment for running your software. In other words, your customers will be running the exact code you've tested.

The RTE is smaller than the SDK. The RTE contains everything your users will need to run your software, but it leaves out the development tools and demo applets and applications that are part of the SDK. Because the RTE is relatively small, it's easier for you to package with your software or for your users to download themselves from our web site.

Table 2 lists the notable differences between the RTE and the SDK:

Table 2: Differences Between the RTE and the SDK

RTE SDK

Class libraries to use JAVAPLUGIN.JAR JAVAPLUGIN.JAR

RT.JAR RT.JAR

HTMLCONVERTER.JAR

I18N.JAR (optional) I18N.JAR

SUNRSASIGN.JAR SUNRSASIGN.JAR

DT.JAR

TOOLS.JAR

May be redeployed by vendors. May NOT be redeployed by vendors.

They are missing the Main.class for javac, jar, javadoc, native2ascii, rmic, etc.

Shareable libraries JAVA$AGENT_G_SHR.EXE

JAVA$AGENT_SHR.EXE

JAVA$AWT_G_SHR.EXE

JAVA$AWT_SHR.EXE JAVA$AWT_SHR.EXE

   JAVA$CMM_G_SHR.EXE

   JAVA$CMM_SHR.EXE JAVA$CMM_SHR.EXE

   JAVA$DCPR_G_SHR.EXE

   JAVA$DCPR_SHR.EXE JAVA$DCPR_SHR.EXE

   JAVA$DT_SOCKET_G_SHR.EXE

   JAVA$DT_SOCKET_SHR.EXE

   JAVA$FONTMANAGER_G_SHR.EXE

   JAVA$FONTMANAGER_SHR.EXE JAVA$FONTMANAGER_SHR.EXE

JAVA$FVM_G_SHR.EXE

JAVA$FVM_SHR.EXE JAVA$FVM_SHR.EXE

   JAVA$HPI_G_SHR.EXE

   JAVA$HPI_SHR.EXE JAVA$HPI_SHR.EXE

   JAVA$HPROF_G_SHR.EXE

   JAVA$HPROF_SHR.EXE JAVA$HPROF_SHR.EXE

JAVA$IOSER12_G_SHR.EXE

JAVA$IOSER12_SHR.EXE JAVA$IOSER12_SHR.EXE

JAVA$JAVA_G_SHR.EXE

JAVA$JAVA_SHR.EXE JAVA$JAVA_SHR.EXE

JAVA$JAVA_VMS_G_SHR.EXE

JAVA$JAVA_VMS_SHR.EXE JAVA$JAVA_VMS_SHR.EXE

JAVA$JAWT_G_SHR.EXE

JAVA$JAWT_SHR.EXE JAVA$JAWT_SHR.EXE

JAVA$JCOV_G_SHR.EXE

JAVA$JCOV_SHR.EXE JAVA$JCOV_SHR.EXE

JAVA$JDWP_G_SHR.EXE

JAVA$JDWP_SHR.EXE

JAVA$JIT_131_G_SHR.EXE

JAVA$JIT_131_SHR.EXE JAVA$JIT_131_SHR.EXE

JAVA$JPEG_G_SHR.EXE

JAVA$JPEG_SHR.EXE JAVA$JPEG_SHR.EXE

JAVA$JSOUND_G_SHR.EXE

JAVA$JSOUND_SHR.EXE JAVA$JSOUND_SHR.EXE

JAVA$JVM_G_SHR.EXE

JAVA$JVM_SHR.EXE JAVA$JVM_SHR.EXE

JAVA$MAWT_G_SHR.EXE

JAVA$MAWT_SHR.EXE JAVA$MAWT_SHR.EXE

JAVA$MLIB_IMAGE_G_SHR.EXE

JAVA$MLIB_IMAGE_SHR.EXE JAVA$MLIB_IMAGE_SHR.EXE

JAVA$NET_G_SHR.EXE

JAVA$NET_SHR.EXE JAVA$NET_SHR.EXE

JAVA$VERIFY_G_SHR.EXE

JAVA$VERIFY_SHR.EXE JAVA$VERIFY_SHR.EXE

JAVA$ZIP_G_SHR.EXE

JAVA$ZIP_SHR.EXE JAVA$ZIP_SHR.EXE

LIBJAVAPLUGIN_JNI LIBJAVAPLUGIN_JNI

LIBJAVAPLUGIN_OJI.EXE LIBJAVAPLUGIN_OJI.EXE

LIBJAVAPLUGIN_OJI.SO LIBJAVAPLUGIN_OJI.SO

Main Programs Deployed in Kit

JAVA$APPLETVIEWER.EXE

JAVA$APPLETVIEWER_G.EXE

JAVA$APPLETVIEWER_G_DEBUG.EXE

JAVA$EXTCHECK.EXE

JAVA$EXTCHECK_G.EXE

JAVA$EXTCHECK_G_DEBUG.EXE

JAVA$IDLJ.EXE

JAVA$IDLJ_G.EXE

JAVA$IDLJ_G.DEBUG.EXE

JAVA$JAR.EXE

JAVA$JAR_G.EXE

JAVA$JAR_G_DEBUG.EXE

JAVA$JARSIGNER.EXE

JAVA$JARSIGNER_G.EXE

JAVA$JARSIGNER_G_DEBUG.EXE

JAVA$JAVA.EXE JAVA$JAVA.EXE

JAVA$JAVA_G.EXE

JAVA$JAVA_G_DEBUG.EXE

JAVA$JAVAC.EXE

JAVA$JAVAC_G.EXE

JAVA$JAVAC_G_DEBUG.EXE

JAVA$JAVADOC.EXE

JAVA$JAVADOC_G.EXE

JAVA$JAVADOC_G_DEBUG.EXE

JAVA$JAVAH.EXE

JAVA$JAVAH_G.EXE

JAVA$JAVAH_G_DEBUG.EXE

JAVA$JAVAP.EXE

JAVA$JAVAP_G.EXE

JAVA$JAVAP_G_DEBUG.EXE

JAVA$JDB.EXE

JAVA$JDB_G.EXE

JAVA$JDB_G_DEBUG.EXE

JAVA$KEYTOOL.EXE JAVA$KEYTOOL.EXE

JAVA$KEYTOOL_G.EXE

JAVA$KEYTOOL_G_DEBUG.EXE

JAVA$NATIVE2ASCII.EXE

JAVA$NATIVE2ASCII_G.EXE

JAVA$NATIVE2ASCII_G_DEBUG.EXE

JAVA$OLDJAVA.EXE

JAVA$OLDJAVA_G.EXE

JAVA$OLDJAVA_G_DEBUG.EXE

JAVA$OLDJAVAC.EXE

JAVA$OLDJAVAC_G.EXE

JAVA$OLDJAVAC_G_DEBUG.EXE

JAVA$OLDJDB.EXE

JAVA$OLDJDB_G.EXE

JAVA$OLDJDB_G_DEBUG.EXE

JAVA$POLICYTOOL.EXE JAVA$POLICYTOOL.EXE

JAVA$POLICYTOOL_G.EXE

JAVA$POLICYTOOL_G_DEBUG.EXE

JAVA$RMIC.EXE

JAVA$RMIC_G.EXE

JAVA$RMIC_G_DEBUG.EXE

JAVA$RMID.EXE JAVA$RMID.EXE

JAVA$RMID_G.EXE

JAVA$RMID_G_DEBUG.EXE

JAVA$RMIREGISTRY.EXE JAVA$RMIREGISTRY.EXE

JAVA$RMIREGISTRY_G.EXE

JAVA$RMIREGISTRY_G_DEBUG.EXE

JAVA$SERIALVER.EXE

JAVA$SERIALVER_G.EXE

JAVA$SERIALVER_G_DEBUG.EXE

JAVA$TNAMESERV.EXE JAVA$TNAMESERV.EXE

JAVA$TNAMESERV_G.EXE

JAVA$TNAMESERV_G_DEBUG.EXE

Kit makeup Two separate BACKUP save sets -- one required, one optional. Vendor downloads and unpacks. No debug images or documentation. Single downloadable entity, including some documentation. (API Reference info in separate kit). Installation of debug images is optional.

Not intended for end-user installation. Intended for end-user.

Uses BACKUP for unpacking. Uses PRODUCT to unpack and install.

Installation No installation per se. User manually unpacks into [.bin] and [.lib] within his application tree of files. Installs like any other OpenVMS product.

Integration with vendor's product Intended to be tightly integrated with vendor's product and shipped with vendor's application kit. Not integrated with any application. It is installed by end user into his environment independent of any application.

For more information on bundling an application in a Java Archive (JAR) file, refer to Packaging Your Application in a JAR File on Sun's site.

When bundling the RTE with application software on the OpenVMS Alpha platform, the following points should be considered:

Software vendors should bundle the RTE files and an installer with the Java software they supply to end-users. Compaq suggests that the RTE be installed in its own subdirectory (called <JRE_RUNTIME_BASE> in Figure 1). This allows you to update the RTE independently of updates to your application, and vice versa.
In addition to unpacking the files in the RTE, a number of symbols and logicals need to be set up to make your application run within the RTE. When you deploy your application, you will have to include your own .COM files that accomplish these setups. An RTE setup command file, JAVA$131_JRE_SETUP.COM, is deposited into the [.LIB] directory, resulting from restoring JRE-V131-3.A. This file contains the key commands you will need to merge into your application setup command file.
The RTE operates with a special set of class libraries -- RT.JAR and (optionally) I18N.JAR. Your application must function with just these libraries.
You are not allowed to redistribute any class files from the Compaq SDK, and your application should have no dependencies on these files. You can redistribute the jar files that are part of the RTE.
Compaq recommends that you not rely on the CLASSPATH logical that might be on the target system, but explicitly identify the classpath by specifying the -cp option on the Java command line that invokes the RTE. (For more information on using the -cp option of the Java command, refer to "Tool Documentation" in the Supplementary Documentation section of the Index page of SDK v 1.3.1.)

Hence, a typical Java command line when using the RTE will look like:
$ JAVA -cp "/USER1$/APP-DIR/LIB/APPLICATION.JAR:." "Application"

Compaq Registered in U.S. Patent and Trademark Office.

Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

All other product names mentioned herein may be trademarks or registered trademarks of their respective companies.

Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is subject to change without notice.

	RTE	SDK
Class libraries to use	JAVAPLUGIN.JAR	JAVAPLUGIN.JAR
	RT.JAR	RT.JAR
		HTMLCONVERTER.JAR
	I18N.JAR (optional)	I18N.JAR
	SUNRSASIGN.JAR	SUNRSASIGN.JAR
		DT.JAR
		TOOLS.JAR
	May be redeployed by vendors.	May NOT be redeployed by vendors.
	They are missing the Main.class for javac, jar, javadoc, native2ascii, rmic, etc.
Shareable libraries		JAVA$AGENT_G_SHR.EXE
		JAVA$AGENT_SHR.EXE
		JAVA$AWT_G_SHR.EXE
	JAVA$AWT_SHR.EXE	JAVA$AWT_SHR.EXE
		JAVA$CMM_G_SHR.EXE
	JAVA$CMM_SHR.EXE	JAVA$CMM_SHR.EXE
		JAVA$DCPR_G_SHR.EXE
	JAVA$DCPR_SHR.EXE	JAVA$DCPR_SHR.EXE
		JAVA$DT_SOCKET_G_SHR.EXE
		JAVA$DT_SOCKET_SHR.EXE
		JAVA$FONTMANAGER_G_SHR.EXE
	JAVA$FONTMANAGER_SHR.EXE	JAVA$FONTMANAGER_SHR.EXE
		JAVA$FVM_G_SHR.EXE
	JAVA$FVM_SHR.EXE	JAVA$FVM_SHR.EXE
		JAVA$HPI_G_SHR.EXE
	JAVA$HPI_SHR.EXE	JAVA$HPI_SHR.EXE
		JAVA$HPROF_G_SHR.EXE
	JAVA$HPROF_SHR.EXE	JAVA$HPROF_SHR.EXE
		JAVA$IOSER12_G_SHR.EXE
	JAVA$IOSER12_SHR.EXE	JAVA$IOSER12_SHR.EXE
		JAVA$JAVA_G_SHR.EXE
	JAVA$JAVA_SHR.EXE	JAVA$JAVA_SHR.EXE
		JAVA$JAVA_VMS_G_SHR.EXE
	JAVA$JAVA_VMS_SHR.EXE	JAVA$JAVA_VMS_SHR.EXE
		JAVA$JAWT_G_SHR.EXE
	JAVA$JAWT_SHR.EXE	JAVA$JAWT_SHR.EXE
		JAVA$JCOV_G_SHR.EXE
	JAVA$JCOV_SHR.EXE	JAVA$JCOV_SHR.EXE
		JAVA$JDWP_G_SHR.EXE
		JAVA$JDWP_SHR.EXE
		JAVA$JIT_131_G_SHR.EXE
	JAVA$JIT_131_SHR.EXE	JAVA$JIT_131_SHR.EXE
		JAVA$JPEG_G_SHR.EXE
	JAVA$JPEG_SHR.EXE	JAVA$JPEG_SHR.EXE
		JAVA$JSOUND_G_SHR.EXE
	JAVA$JSOUND_SHR.EXE	JAVA$JSOUND_SHR.EXE
		JAVA$JVM_G_SHR.EXE
	JAVA$JVM_SHR.EXE	JAVA$JVM_SHR.EXE
		JAVA$MAWT_G_SHR.EXE
	JAVA$MAWT_SHR.EXE	JAVA$MAWT_SHR.EXE
		JAVA$MLIB_IMAGE_G_SHR.EXE
	JAVA$MLIB_IMAGE_SHR.EXE	JAVA$MLIB_IMAGE_SHR.EXE
		JAVA$NET_G_SHR.EXE
	JAVA$NET_SHR.EXE	JAVA$NET_SHR.EXE
		JAVA$VERIFY_G_SHR.EXE
	JAVA$VERIFY_SHR.EXE	JAVA$VERIFY_SHR.EXE
		JAVA$ZIP_G_SHR.EXE
	JAVA$ZIP_SHR.EXE	JAVA$ZIP_SHR.EXE
	LIBJAVAPLUGIN_JNI	LIBJAVAPLUGIN_JNI
	LIBJAVAPLUGIN_OJI.EXE	LIBJAVAPLUGIN_OJI.EXE
	LIBJAVAPLUGIN_OJI.SO	LIBJAVAPLUGIN_OJI.SO
Main Programs Deployed in Kit
		JAVA$APPLETVIEWER.EXE
		JAVA$APPLETVIEWER_G.EXE
		JAVA$APPLETVIEWER_G_DEBUG.EXE
		JAVA$EXTCHECK.EXE
		JAVA$EXTCHECK_G.EXE
		JAVA$EXTCHECK_G_DEBUG.EXE
		JAVA$IDLJ.EXE
		JAVA$IDLJ_G.EXE
		JAVA$IDLJ_G.DEBUG.EXE
		JAVA$JAR.EXE
		JAVA$JAR_G.EXE
		JAVA$JAR_G_DEBUG.EXE
		JAVA$JARSIGNER.EXE
		JAVA$JARSIGNER_G.EXE
		JAVA$JARSIGNER_G_DEBUG.EXE
	JAVA$JAVA.EXE	JAVA$JAVA.EXE
		JAVA$JAVA_G.EXE
		JAVA$JAVA_G_DEBUG.EXE
		JAVA$JAVAC.EXE
		JAVA$JAVAC_G.EXE
		JAVA$JAVAC_G_DEBUG.EXE
		JAVA$JAVADOC.EXE
		JAVA$JAVADOC_G.EXE
		JAVA$JAVADOC_G_DEBUG.EXE
		JAVA$JAVAH.EXE
		JAVA$JAVAH_G.EXE
		JAVA$JAVAH_G_DEBUG.EXE
		JAVA$JAVAP.EXE
		JAVA$JAVAP_G.EXE
		JAVA$JAVAP_G_DEBUG.EXE
		JAVA$JDB.EXE
		JAVA$JDB_G.EXE
		JAVA$JDB_G_DEBUG.EXE
	JAVA$KEYTOOL.EXE	JAVA$KEYTOOL.EXE
		JAVA$KEYTOOL_G.EXE
		JAVA$KEYTOOL_G_DEBUG.EXE
		JAVA$NATIVE2ASCII.EXE
		JAVA$NATIVE2ASCII_G.EXE
		JAVA$NATIVE2ASCII_G_DEBUG.EXE
		JAVA$OLDJAVA.EXE
		JAVA$OLDJAVA_G.EXE
		JAVA$OLDJAVA_G_DEBUG.EXE
		JAVA$OLDJAVAC.EXE
		JAVA$OLDJAVAC_G.EXE
		JAVA$OLDJAVAC_G_DEBUG.EXE
		JAVA$OLDJDB.EXE
		JAVA$OLDJDB_G.EXE
		JAVA$OLDJDB_G_DEBUG.EXE
	JAVA$POLICYTOOL.EXE	JAVA$POLICYTOOL.EXE
		JAVA$POLICYTOOL_G.EXE
		JAVA$POLICYTOOL_G_DEBUG.EXE
		JAVA$RMIC.EXE
		JAVA$RMIC_G.EXE
		JAVA$RMIC_G_DEBUG.EXE
	JAVA$RMID.EXE	JAVA$RMID.EXE
		JAVA$RMID_G.EXE
		JAVA$RMID_G_DEBUG.EXE
	JAVA$RMIREGISTRY.EXE	JAVA$RMIREGISTRY.EXE
		JAVA$RMIREGISTRY_G.EXE
		JAVA$RMIREGISTRY_G_DEBUG.EXE
		JAVA$SERIALVER.EXE
		JAVA$SERIALVER_G.EXE
		JAVA$SERIALVER_G_DEBUG.EXE
	JAVA$TNAMESERV.EXE	JAVA$TNAMESERV.EXE
		JAVA$TNAMESERV_G.EXE
		JAVA$TNAMESERV_G_DEBUG.EXE
Kit makeup	Two separate BACKUP save sets -- one required, one optional. Vendor downloads and unpacks. No debug images or documentation.	Single downloadable entity, including some documentation. (API Reference info in separate kit). Installation of debug images is optional.
	Not intended for end-user installation.	Intended for end-user.
	Uses BACKUP for unpacking.	Uses PRODUCT to unpack and install.
Installation	No installation per se. User manually unpacks into [.bin] and [.lib] within his application tree of files.	Installs like any other OpenVMS product.
Integration with vendor's product	Intended to be tightly integrated with vendor's product and shipped with vendor's application kit.	Not integrated with any application. It is installed by end user into his environment independent of any application.

Readme Compaq Run Time Environment (RTE) v 1.3.1-3 for the OpenVMS Operating System for the Java™ Platform

Contents