

                        VisualAge(R) for Java(TM)
                               Version 3.0
 
                               Online Help

                              RELEASE NOTES

Table of Contents
-----------------

For all platforms

1.0 Corrections to the documentation
2.0 JDK and JFC API reference documentation 
    is not searchable

For Windows (R)

1.0 Installing to a LAN drive
2.0 Installing and configuring TCP/IP
3.0 Changing to a different port number 
4.0 Changing to a different browser
5.0 Uninstalling a second instance of VisualAge for Java

For AIX (R)

1.0 Search in DBCS languages is currently inoperative
2.0 IMNSearch fileset installation
3.0 Help browser requirements
4.0 Problems with Netscape 
5.0 Debugger help is not searchable

For OS/2 (R)

1.0 Installing the HTML Search System
    1.1 Installation requirements on OS/2 4.0 or 4.1
    1.2 Locating the Search System Directory
    1.3 Installing on a system that VisualAge for C++ is installed on 
    1.4 Changing to a Different Port Number 
    1.5 x.x DBCS search fix
2.0 Using the HTML Search System
    2.1 Browser requirements
    2.2 TCP/IP configuration



For all platforms
=================

1.0 Corrections to the documentation

In the online help Search help file, the line "To search for an exact 
phrase, enclose the phrase in quotation marks (" ")" should be "To 
search for an exact phrase, precede the phrase with a plus sign (+), 
then enter the exact phrase with quotation marks around it (+" ").

2.0 JDK and JFC API reference documentation is not searchable

The following text is applicable to all platforms, Professional and 
Enterprise editions, for all languages except English:

The JDK and JFC API reference documentation is not searchable.
For versions of VisualAge for Java in languages other than English, 
searching for terms in the JDK and JFC API reference documentation 
will return no hits.

For Windows
===========

1.0 Installing to a LAN drive
-----------------------------

If you install to a LAN drive "X:", your AUTOEXEC.BAT call to the
search system "X:\IMNNQ_YY\IMNENV.BAT" -- where "YY" is either "95"
or "NT" or "98" -- will fail.  Please copy this file to your Windows
drive "C:" and edit AUTOEXEC.BAT to call "C:\IMNNQ_YY\IMNENV.BAT"

2.0 Installing and configuring TCP/IP
-------------------------------------
  TCP/IP must be installed and configured in order for the online 
  help to function properly. For Windows 95 and 98, TCP/IP must 
  be enabled as follows:

  1. For a LAN Adapter configuration:
        - You must have DNS enabled with a valid host and domain name.

  2. For a Dial-Up Adapter configuration:
        - You must have DNS disabled.
        - Your TCP/IP address must be obtained automatically.
        Note: These configuration options will apply to all TCP/IP
        adapters even though they have only been changed for this one.
        You will not be able to use both LAN and Dial-Up without
        reconfiguring.

Dial-Up networking TCP/IP properties for your Internet service provider(s)
(ISP) must be configured as documented by the ISP. The Dial-Up networking
TCP/IP properties will override the properties in the Dial-Up Adapter 
TCP/IP properties configured via the 'Network' icon in the Windows 95/98
Control Panel.  The overriding of the properties will take place only 
if the Dial-Up Adapter TCP/IP properties are configured as above. 
You must not enable the DNS in the Dial-Up Adapter TCP/IP properties 
or set an IP address in the Dial-Up Adapter TCP/IP properties. Doing so
will interfere with the Dial-Up networking configuration for the ISP.

The above configurations also apply For Windows NT 4.0.  If you are
running standalone, you can also enable the MS Loopback Adapter
without the other two adapters.

3.0 Changing to a different port number
--------------------------------------

The help system is assigned to port 49213, a number beyond the 
public ports assigned for TCP/IP.  If you have another product that
uses this port, or if you cannot connect to this port, you can 
change the help system port with the following steps:

   1. Edit the httpd.cnf file in the IMNNQ_NT or IMNNQ_95 directory 
      and change the port number to one you know is available, 
      preferably above 49000.

   2. In the c:\IBMJAVA\doc\ivjhlp.cfg file, where c:\IBMJAVA is the 
      VisualAge for Java installation directory, edit the HTML_HOSTNAME 
      value. This value reads, by default:

      localhost:49213

      Edit this value so that the port number you selected in step 1 
      replaces 49213.

   3. Go to the VisualAge for Java installation directory.  In the doc
      subdirectory, you will find the following files:
      
      hgssrch.htm     hgcsrch.htm

   4. Use a text editor to edit the hgssrch.htm file to change the
      following line in hgssrch.htm, so that the port number you 
      selected in step 1 replaces 49213 below:

     <form action="http://localhost:49213/cgi-bin/ivjsrch.exe"
      METHOD="POST">

     Repeat this action for the hgcsrch.htm file.      

     Use your zip tool to update the edited files into the file main.zip.

    NOTE: PLEASE UPDATE/ADD THE NEW FILES WITH NO COMPRESSION AND NO PATH
    INFORMATION.
    The files inside the zip file are not compressed.  If you compress the
    file when you update it, you will see only random characters when you
    reload the search form.

   5. Clear your browser memory and disk cache, and exit VisualAge for Java.  
      Help and search should now connect on the new port.

4.0 Changing to a different browser
-----------------------------------

By default, VisualAge for Java uses your system's default (Netscape
or Internet Explorer) browser to display help. You must modify the 
help system configuration file if you would like to use a browser 
other than the default browse browser for your computer.  Attempting
to change the browser from the Help page of the Options dialog 
currently has no effect. You can change the browser used by the help 
system with the following steps:
   
   1. Use a text editor to edit the C:\IBMVJava\doc\ivjhlp.cfg file,
      where C:\IBMVJava is the VisualAge for Java installation
      directory.

   2. Remove the # character from the beginning of the line 
      #HTML_BROWSER="H:\Programs\Netscape\Communicator\Netscape.exe"

   3. Replace H:\Programs\Netscape\Communicator\Netscape.exe with the 
      path and file name of your preferred browser.

   4. Save and close the ivjhlp.cfg file.

   5. Start VisualAge for Java. Help should now use your preferred 
      browser.

5.0 Uninstalling a second instance of VisualAge for Java
--------------------------------------------------------

After uninstalling a second instance of VisualAge for Java, the 
search function of the help system does not work.  You need to 
update the first, original instance by reinstalling VisualAge for
Java. Once you have reinstalled VisualAge for Java, the search function
will work normally.

For AIX
=======

1.0 Search in DBCS languages is currently inoperative
-----------------------------------------------------
The search function in Japanese, Korean, simplified Chinese, and 
traditional Chinese is currently inoperative.  The "File Not Found"
error message is an expected result.


2.0 IMNSearch fileset installation
----------------------------------

If there is an existing product on your system that uses a previous 
version of the IMNSearch filesets, such as DB2 5.x, the help system 
will not install. The help system is comprised of the IBMVJava.html.*,
IMNSearch.*, and vatools.* filesets. You need to uninstall VisualAge
for Java, and then explicitly select the IMNSearch filesets to make 
sure they install correctly when you re-install VisualAge for Java.
See the instructions in the AIX Readme for details.  

If you experience a problem installing the IMNSearch component, please
completely remove the component before trying to re-install.

Note that this only applies to new installs of the IMNSearch component.
If you already have a previous version of the IMNSearch component,
you should not remove the component before trying to re-install.  

3.0 Help browser requirements
-----------------------------
IBM(R) HTML help requires a frames-supporting browser such as 
Netscape Navigator version 3.0 or above. For best results, we recommend
you use Netscape 4.0 or above. Please note that we only 
support Netscape Navigator and no other browsers.
You should ensure you do not have the environment variable 
SOCKS_NS set. This setting can cause Netscape to hang. 
This variable is sometimes left over from Netscape 3.0 when
upgrading to Netscape 4.0 or above.

The browser that you use must not have proxy handling for the
localhost port. If you are using Netscape's automatic proxy
configuration, talk to your system administrator to find out
whether 127.0.0.1 and localhost are handled as proxy
exceptions (they should be). Your system administrator can
configure the proxy settings so that HTML help will work.
 
If you are setting proxy or socks services manually, ensure
you turn off proxy handling for localhost in the browser you use.

To do this in Netscape 3, follow these steps:

1. Select Options... Network Preferences...
2. Click the Proxies tab
3. Click View at the Manual Proxy Configuration selection
4. Type: 

localhost:49213,127.0.0.1

in the "No proxies for" box. If you have other entries here, separate 
the new entry with a comma.

5. Click OK, then click OK to exit the Proxies tab.

To do this in Netscape 4 (Communicator), follow these steps:

1. Select Edit... Preferences..
2. Double-click Advanced in the Category tree
3. Click Proxies in the Advanced subtree
4. Click View at the Manual Proxy Configuration selection.
5. Type: 

localhost:49213,127.0.0.1

in the "Exceptions... Do not use proxy servers for domains beginning 
with" box. If you have other entries here, separate the new entry
with a comma.

6. Click OK, then click OK to exit the Preferences Window.

4.0 Problems with Netscape 
--------------------------

Certain versions of Netscape Communicator 4.x have a 
problem with HTML frames when they are first loaded. Restarting the 
browser should enable you to workaround this problem, and 
subsequent calls to framesets will display properly.  

5.0 Debugger help is not searchable
-----------------------------------

Searching for terms in debugger documentation will return
no hits. 

For OS/2
========

1.0 Installing the HTML search system
-------------------------------------

1.1 Installation requirements on OS/2 4.0 or 4.1

The search server (that is included with IBM VisualAge for Java for OS/2)
requires that OS/2 TCP/IP is configured and functional. The search server
will function with or without a network adapter installed as long as
TCP/IP is configured with the following:

      a) Local loopback is enabled.
      b) Localhost is enabled on your system.

See section 2.2 for information on TCP/IP configuration.

1.2 Locating the search system directory

The search system is stored in its own directory since it may be used by
other products. To locate this directory, issue the command:

echo %IMNNLPSSRV%

The search system directory is located at the root of the drive
that VisualAge for Java was installed in.

1.3 Installing on a system that VisualAge for C++ is installed on 

If you are installing VisualAge for Java on a system that has VisualAge for C++ for OS/2, you need to have CSD6 or above installed for the VisualAge
for C++ product.


1.4 Changing to a Different Port Number (OS/2)

The help system is assigned to port 49213, a number beyond the public
ports assigned for TCP/IP.  If you have another product that uses this port, or if you cannot connect to this port, you can change the help system port with the following steps:

1. Edit the httpd.cnf file in the NETQOS2 directory and change the port    number to one that you know is available, preferably above 49000.

2. In the c:\IBMJAVA\doc\ivjhlp.cfg file, where c:\IBMJAVA is the 
   VisualAge for Java installation directory, edit the HTML_HOSTNAME 
   value. This value reads, by default:

   localhost:49213

      Edit this value so that the port number you selected in step 1 
      replaces 49213.

   3. Go to the VisualAge for Java installation directory.  In the doc
      subdirectory, you will find the following files:
      
      hgssrch.htm     hgcsrch.htm

   4. Use a text editor to edit the hgssrch.htm file to change the
      following line in hgssrch.htm, so that the port number you 
      selected in step 1 replaces 49213 below:

     <form action="http://localhost:49213/cgi-bin/ivjsrch.exe"
      METHOD="POST">

     Repeat this action for the hgcsrch.htm file.      

     Use your zip tool to update the edited files into the file main.zip.

    NOTE: PLEASE UPDATE/ADD THE NEW FILES WITH NO COMPRESSION AND NO PATH
    INFORMATION.
    The files inside the zip file are not compressed.  If you compress     
    the file when you update it, you will see only random characters when you
    reload the search form.

   5. Clear your browser memory and disk cache, and exit VisualAge for
      Java. Help and search should now connect on the new port.

1.5 DBCS search fix

In double-byte versions of VisualAge for Java, searches for double-byte character
terms will fail. To fix this, edit the file IBMVJava\doc\hgcsrch.htm in a text editor.  

Delete the following lines:
        <input type=hidden name=SelectIndex value=ivj3ujdk>
        <input type=hidden name=SelectIndex value=ivj3ujfc>

Also delete these two lines from the file IBMVJava\doc\hgssrch.htm.

2.0 Using the HTML search system
--------------------------------

2.1 Browser requirements

VisualAge for Java HTML help requires a frames-supporting browser such as
Netscape Navigator for OS/2, Version 2.02 or 4.04. Please note that we 
only support Netscape Navigator. 

The browser that you use must not have proxy handling for the localhost
port.

If you did not elect to allow the installation process to automatically
configure your browser, please follow these instructions.

  1) Launch Netscape.
  2) Under the Options menu, select Network Preferences.
  3) Select the Proxy tab.
  4) Add localhost:49213 to your proxy exception text box.

2.2 TCP/IP configuration

     a) Enable local loopback by following these steps:
        1) Open the OS/2 TCP/IP folder.
        2) Open the TCP/IP Configuration notebook.
        3) View the Network page.
        4) In the listbox labelled "Interface to Configure", highlight the
           item labelled "loopback interface".
        5) Verify that the checkbox on the right labelled "Enable interface"
           is selected.
        6) With "loopback interface" still highlighted, verify that the entry
           field for "IP address" is 127.0.0.1 and "Subnet Mask" is empty.

      b) Verify that localhost is enabled on your system::
         
         1. On any OS/2 command line enter "ping localhost". This command
            should return some data back. If it hangs, or if it returns 
            "localhost unknown", then localhost has not been enabled on your
            system. If you are on a network, then ensure that loopback is 
            enabled. If you are not on a network, enable localhost by following
            these steps:

           a) Add the line:

              ifconfig lo 127.0.0.1

              to MPTN\BIN\setup.cmd.  Add the line after other ifconfig lines
              in the command file.

           b) In TCP/IP configuration:
                 1. Go to the "Configure Name Resolution Services" page
                    (page 2 of Hostnames).
                 2. Add an entry to the table titled:  "Hostname configuration
                    without a Nameserver" with IP Address set as 127.0.0.1 and
                    Hostname set to localhost.
                 3. Select the check box underneath the table labeled:
                    "Look through HOSTS list before going to nameserver."
                    This will enable localhost to bypass any nameserver to
                    resolve the name.
                 4. Close TCP/IP configuration and reboot the system. You
                    should be able to ping localhost without being connected to
                    any network. If ping localhost still hangs, delete
                    rid of any nameservers in the TCP/IP configuration so that
                   name resolution can only go through looking at the HOSTS
                   list.




