United States

Mozilla™ Technology Demonstration Release
for OpenVMS™ Alpha™ Release Notes

February 16, 2001

Mozilla M0.8
CPQ-AXPVMS-MOZILLA-M0008--1.PCSI

On this page you'll find information about:

Before Installing Mozilla

• Hardware and Software Prerequisites
  
• Account Quotas and System Parameters
  
• Mozilla.org Release Notes
  
• Upgrading from a Previous Kit
  

Downloading and Installing Mozilla

• Downloading the Kit
  
• Expanding the Kit
  
• Installing Mozilla
  
• Stopping and Restarting the Installation
  
• Installing the Mozilla Images
  

Running Mozilla

• Invoking Mozilla-bin
  
• Setting Up a Helper Application (Example: Adobe™ Acrobat™ Viewer for Java™)
  

Release Notes

Performance Notes

Frequently Asked Questions (FAQ)

Problem Reporting and Bugzilla

• OpenVMS Version 7.1 or higher.
• OpenVMS Version 7.2 -- No patches (ECOs) needed.
• OpenVMS Version 7.1-2 -- Requires VMS712_PTHREADS-V0300 patch.
• OpenVMS Version 7.1, 7.1-1H1 and 7.1-1H2 -- Require ALPLIBR08_071 patch and the Java™/FastTrack® set of patches.

  For more information about downloading patches, see Compaq Services Software Patches.

• DECwindows MOTIF V1.2-4 or higher
• TCP/IP Services for OpenVMS:

• Version 4.2 ECO 3
• Version 5.0A

Mozilla for OpenVMS has not been tested with any other IP stack.

Mozilla requires a relatively large number of process sections, so you may find that you have an insufficient number. (Note: If you install the Mozilla images after you install the Mozilla kit, you can avoid this problem completely. See Installing the Mozilla Images for more information.)

If you see an error similar to either of the following, then you have exhausted the available process sections:

nsNativeComponentLoader: GetFactory(/dka0/mozilla/components/libnsgif.so) Load FAILED with error: OpenVMS status is decimal 540 %SYSTEM-F-SECTBLFUL, process or global section table is full

There are three ways to solve this problem, as follows:

• Install the Mozilla images. This is the preferred solution.

• Increase the difference between WSEXTENT and WSMAX. For example, if your WSEXTENT and WSMAX values are both set to 65536, increase WSMAX to 131072 or decrease WSEXTENT to 32768. Because WSEXTENT is a per-user value, this is the preferred solution if you cannot install the images.

• Increase the SYSGEN parameter PROCSECTCNT. However, PROCSECTCNT affects every process on the system so this may not be a very desirable solution.

Mozilla.org has provided release notes for M0.8.

The release notes contain sections about Mozilla on Windows®, Mac®, and UNIX®. Mozilla for OpenVMS is ported from the UNIX code, so the notes in the UNIX section are applicable to OpenVMS.

When reading UNIX documentation, note the following differences between UNIX and OpenVMS:

• File specification format

  The mozilla.org release notes show example file specifications in UNIX format. For example, the UNIX file specification /dka100/foo/bar/file.dat is equivalent to DKA100:[FOO.BAR]FILE.DAT on OpenVMS.

• Directory format

  Directories that begin with a period on UNIX begin with an underscore on OpenVMS. In addition, on UNIX, the tilde (~) is shorthand for SYS$LOGIN. Therefore, on UNIX ~/.mozilla/mozprofile/prefs.js is equivalent to [._MOZILLA.MOZPROFILE].

Please fill out and submit the Mozilla for OpenVMS registration form. You will receive an email message with the URL of the location of the kit to download.

The size of the compressed kit is 42,932 blocks. The expanded kit will occupy 118,800 blocks.

After you expand the Mozilla kit, you can delete the .SFX_AXPEXE file. Alternatively, you can first install Mozilla, then delete the .PCSI file, and keep the small .SFX_AXPEXE file in case you need to re-install the Mozilla kit.

Installing Mozilla

Stopping and Restarting the Installation

Use the following procedure to stop and restart the installation:

1. To stop the procedure at any time, press Ctrl/Y.

2. Enter the DCL command PRODUCT REMOVE to reverse any changes to the system that occurred during the partial installation. This deletes all files created up to that point and causes the installation procedure to exit.

3. Go back to the beginning of the installation procedure to restart the installation.

Installing the Mozilla Images

After you install Mozilla using the PRODUCT INSTALL command, you can also optionally install the Mozilla images. There are two benefits to installing the images:

• If several users on the same system are using Mozilla, you make better use of system resources and improve performance.

• Installing the images avoids the problem of running out of Process Sections (described in Account Quotas and System Parameters.) If you install the images, the problem is eliminated.

To install the Mozilla images, run the command file INSTALL.COM (which resides in the Mozilla root directory). For example:

$ SET DEFAULT SYS$COMMON:[MOZILLA] $ @INSTALL

Approximately 194 global sections and 60,752 global pages are required to install the Mozilla images. If you want to uninstall the Mozilla images, enter the following:

$ SET DEFAULT SYS$COMMON:[MOZILLA] $ @INSTALL REMOVE

Many other messages are displayed when using the Navigator, Mail/News and Composer components of Mozilla. This is normal for this milestone release.

Setting Up a Helper Application (Example: Adobe™ Acrobat™ Viewer for Java™)

Mozilla for OpenVMS includes support for helper applications. The following example shows how to set up the the Adobe Acrobat Viewer (for Java) on OpenVMS Alpha as a helper application. After completing these steps, when Mozilla encounters a PDF file it will automatically invoke the Acrobat Viewer to display the contents of the PDF file.

1. Install the the Adobe Acrobat Viewer (for Java) on OpenVMS Alpha and check that the viewer is functioning correctly.

2. Create the following file, PDF.COM, in the directory where you have installed the viewer. (The file acrobat.jar should already be in this directory.)

   $ sv = f$verify(0) $ adobe_jar_file = "/dka0/adobeacrobatviewer/acrobat.jar" $ @sys$manager:java$setup $ cp = f$trnlnm("classpath") + ":" + adobe_jar_file $ define /user classpath "''cp'" $ sv = f$verify(sv) $ if "''p2'" .nes. "" then p1 = p2 $ java -mx32m "com.adobe.acrobat.Viewer" 'p1' $ exit

3. Modify the second line of PDF.COM for your system. The value of adobe_jar_file must be the UNIX-style full file specification of the ACROBAT.JAR file. This example uses /dka0/adobeacrobatviewer/acrobat.jar, which is the UNIX-style format of DKA0:[ADOBEACROBATVIEWER].

4. Make sure that the file protection of PDF.COM allows users access to it. For example:

   $ SET FILE /PROTECTION=WORLD:READ DKA0:[ADOBEACROBATVIEWER]PDF.COM

5. The command file PDF.COM can now be used to view any PDF file. Test that you have PDF.COM set up correctly before you configure Mozilla.

   $ SET DEFAULT DKA0:[ADOBEACROBATVIEWER] $ @PDF HELP.PDF

6. Configure Mozilla for the helper application by following these steps:

   • Start Mozilla
   • From the menu bar, select "Edit" and then "Preferences..."
   • From the Navigator section, select "Helper Applications"
   • In the "Helper Applications" area, select "New Type" and enter:

     Description of type: PDF
     File extension: PDF
     MIME type: application/pdf
     Application to use: DKA0:[ADOBEACROBATVIEWER]PDF

     Note that if your viewer directory is not DKA0:[ADOBEACROBATVIEWER], change this value to the correct directory specification. Also note that you can enter the file specification in either OpenVMS or UNIX syntax, or you can use the Choose button to locate your application.

   • Click on OK to close the New Type window
   • Click on OK to close the Preferences window

• Secure Connections via HTTPS Supported

  Mozilla M0.8 for OpenVMS includes support for basic security (https://). This is the first release of Mozilla for OpenVMS to include security support.

  Mozilla M0.8 for OpenVMS provides security using Personal Security Manager (PSM) V2. (Other platforms running Mozilla use PSM V1 to provide security.) PSM V2 is currently under development. When complete, PSM V2 will run in-process as a fully integrated Mozilla component to perform cryptographic operations on behalf of a client application. These operations will include setting up an SSL connection, object signing and signature verification, certificate management (including issuance and revocation), and other common PKI (public-key infrastructure) functions. For more information about PSM, see:

  http://www.mozilla.org/projects/security/pki/psm/

  NOTE: The current baselevel of PSM V2, used by Mozilla M0.8 for OpenVMS, does not include all of the planned functionality. Features that are not yet available include hooks to the user interface (for example, to display a certificate) and error handling. The Mozilla.org release notes that discuss security do not apply to Mozilla for OpenVMS.

• Helper Applications Supported

  Mozilla for OpenVMS supports helper applications. For example, if you want Mozilla to use a PDF viewer to display a PDF file, you would configure the PDF viewer as a helper application.

  See Setting Up a Helper Application for instructions on how to set up the Adobe™ Acrobat™ Viewer for Java™ as a helper application.

This section contains frequently asked questions about Mozilla for OpenVMS Alpha.

Netscape 6 and Communicator 5

Q: What is Netscape 6 and what happened to Communicator Version 5.0?

A: Netscape 6 is the name of the current release of the Netscape browser. (The names Navigator and Communicator are no longer used.) Netscape 6 is based on the Mozilla code base.

Netscape has moved from Communicator Version 4.7 to Netscape 6. There is no Communicator V5.0.

Differences between Mozilla and Netscape 6

Q: What are the differences between Mozilla and Netscape 6?

A: The Netscape 6 browser was built from the Mozilla M18 code. (M18 is the release preceding M0.6.) The M18 code, with the Netscape 6 changes, was released as Mozilla M0.6.

Netscape 6 and Mozilla M0.6 are essentially the same browser, except that Netscape packaged some additional components with their offering.

Netscape 6 contains the following additional components:

• Security component
• AOL Instant Messenger
• AOL branding

Q: Will Netscape 6 be available on OpenVMS?

A: While the actual Netscape 6 product will not be available on OpenVMS, the code base for Netscape 6 is Mozilla M0.6. A newer release of Mozilla, M0.8, is currently available on OpenVMS. Compaq also plans to release a supported version of Mozilla Version 1.0 on OpenVMS.

Security for Mozilla on OpenVMS

Q: When will security be available for Mozilla on OpenVMS?

A: Security support is included in Mozilla M0.8 for OpenVMS, released February 16, 2001. See the Release Notes section for more information.

Mozilla on OpenVMS VAX

Q: When will a version of Mozilla be available for VAX?

A: There are currently no plans to port Mozilla to the VAX platform.

Java Support in Mozilla

Q: Why is there no Java support in Mozilla for OpenVMS?

A: Mozilla implements Java using OJI (Open JVM Integration). OJI is part of Java Version 1.3.0_01, but V1.3.0_01 is not yet available on all platforms, including OpenVMS Alpha. As soon as Java Version 1.3.0_01 is available on OpenVMS, it will be supported in Mozilla. (Note that Java V1.3 is available now on OpenVMS, but it does not include OJI.)

Advantages of using OJI are:

• Multiple Java Virtual Machines (JVMs) can be supported
• Upgrading the JVM used by Mozilla is very easy

For more information, see http://www.mozilla.org/oji/.

Mozilla doesn't start up - decimal error

Q: Mozilla fails to start up. I see errors similar to this displayed:

nsNativeComponentLoader: SelfRegisterDll(/dka0/mozilla/components/libvcard.so) 
Load FAILED with error: OpenVMS status is decimal 114690 

A: One of the account quotas may be too low. See Account Quotas and System Parameters, in particular the discussion about the FILLM quota.

Mozilla doesn't start up - process or global section error

Q: Mozilla fails to start up. I see errors similar to this displayed:

nsNativeComponentLoader: GetFactory(/dka0/mozilla/components/libnsgif.so) 
Load FAILED with error: OpenVMS status is decimal 540 

%SYSTEM-F-SECTBLFUL, process or global section table is full 

A: You have a shortage of process sections. See Account Quotas and System Parameters for information about how to solve this problem.

Can't open new DECterms

Q: After running Mozilla, I can't open any new DECterms. Normal terminal sessions (for example, telnet) still work properly. Only a reboot seems to fix the problem -- removing the installed components from memory (INSTALL.COM REMOVE), or restarting X-Windows does not help. Other X-Windows applications do not seem to be affected. What's going on?

A: You are probably out of buffer object space. Try increasing the SYSGEN parameter MAXBOBMEM.

Unable to open the temporary file

Q: I can't send mail or create a page using Composer. I see a message similar to "Unable to open the temporary file." What's wrong?

A: Make sure that you do not have any logical name or symbol definitions for tmp or tmpdir. If you do, remove them.

Report all problems to Bugzilla. Do not report problems into the PTR system, or in newsgroups, or contact the CSC about Mozilla (Mozilla is not a released product).

Bugzilla

Mozilla has a bug reporting and tracking system named Bugzilla. This system is used to track all Mozilla problems across all platforms, including OpenVMS. For further information on Bugzilla, visit http://www.mozilla.org/bugs/.

Before entering any new problem report, please search the database to make sure that the problem has not already been reported. Mark OpenVMS specific problems by setting the Platform to DEC and OS field to OpenVMS.