Installation and Configuration Supplement

NetQuestion for Windows 32-bit Operating Systems

This section describes post-installation configuration information, additional troubleshooting tips, and workarounds for known issues with NetQuestion on Windows 32-bit operating systems. It also describes how to remove NetQuestion from your system.

Diagnosing NetQuestion Install Errors

If you received error messages while installing NetQuestion, perform the following steps to diagnose and fix the problem:

Look in the <temp>\imnnq\install directory, where <temp> is your system's %TEMP% directory, to find the imnnq.err file. If it does not exist, reboot and try installing the product again. If imnnq.err does exist, here are the possible contents:

   1 - This indicates that the current PATH is too long and adding the search
       server into the PATH will cause the entire PATH to be erased.
       Note:  The limit on Windows NT 4.0 is 512; on Windows 95 it is 255.
       It is recommended that you perform the following steps:
       a) Rename the PATH variable in the AUTOEXEC.BAT file (PATHGOOD), save
          changes and reboot.
       b) Remove the IMNNQ.ERR file from <temp>\imnnq\install.
       c) Run the product install again to install the search system properly.
       d) Merge the PATHGOOD variable with the PATH variable that was created
          by the latest installation.
   2 - Miscellaneous error, please contact IBM service.
   3 - Out of disk space error.  Please ensure that there is at least 4.5MB
       of disk space for the search system plus enough space for AUTOEXEC.BAT
       to be changed for Windows 95.

If imnnq.err contains a message saying <file_name>.EXE DOES NOT EXIST, the NetQuestion executables could not be found. In this case you should try installing the DB2 product documentation again. For more troubleshooting information see Solving Search Problems.

TCP/IP Configuration

The following prerequisites are required to install and work with NetQuestion:

You must have TCP/IP Version 3 or higher installed on your machine. It must be installed and configured in order for NetQuestion to function properly.
For Windows 95 and Windows 98, TCP/IP must be enabled as follows:
- For a LAN Adapter configuration:
  - You must have DNS enabled with a valid host and domain name.
  - Your LAN DNS must resolve localhost to 127.0.0.1.
  - You cannot run disconnected with a LAN adapter configuration.
- 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 (DUN) TCP/IP properties for your internet service provider (ISP) must be configured as documented your ISP. These 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, but only if the Dial-Up Adapter properties are configured as above.
    Note: Do not enable DNS or set an IP address in the Dial-Up Adapter TCP/IP properties as this will interfere with the DUN configuration for the ISP.
For Windows NT 4.0, either TCP/IP configurations (for DUN or Dial-Up Adapter) detailed above will work. If you are running a stand-alone system not connected to a network, you can also enable the MS Loopback Adapter without the other two adapters.

Changing the Port Number for the Search Server

The search server is assigned to port 49213, a number beyond the public ports assigned for TCP/IP. If you have another product that uses this port, you should change the search server port by performing the following steps:

Step  1.
Edit the httpd.cnf file in the NetQuestion directory and change the port number to one you know is available, preferably one above 49000.
Step  2.
Determine where your db2path is by entering the db2set db2path command.
Step  3.
Go to the db2path/doc/html directory and use a text editor to edit the index.htm file. In the line with the <form> tag, change the value for localhost:49213 to reflect the port number you selected in step 1.
Step  4.
Stop and re-start the search server. To stop the search server, click on Start --> Programs --> IBM DB2 --> Stop HTML Search Server. To start the search server, click on Start --> Programs --> DB2 for Windows --> Start HTML Search Server.

Ensuring NetQuestion Environment Variables are set on a LAN-Connected Drive

If you install DB2 on a LAN-connected drive on Windows 9x and the drive is not reconnected before autoexec.bat executes, NetQuestion environment variables are not set. NetQuestion sets environment variables through a batch file (imnenv.bat for SBCS or imqenv.bat for DBCS) that resides in the NetQuestion directory. To bypass this problem, copy imnenv.bat or imqenv.bat from the NetQuestion directory to another drive/directory that is connected before autoexec.bat is executed. Then, modify autoexec.bat to call this batch file on start-up. For example, if you copy imnenv.bat to C:\WINDOWS\IMNNQ, you can add the following line to autoexec.bat:

   IF EXIST C:\WINDOWS\IMNNQ\IMNENV.BAT CALL IMNENV.BAT

Locating the NetQuestion Installation Directory

NetQuestion is stored in its own directory because it may be used by other products. For example, if you installed DB2 Universal Database along with NetQuestion on G\: and later you installed IBM VisualAge for Java on H:\, only one search system is installed, the one that was installed first.

Some instructions in this section require you to specify the location of the NetQuestion directory. To locate this directory enter one of the following commands:

   echo %IMNINSTSRV%       //for SBCS versions
   echo %IMQINSTSRV%       //for DBCS versions

Searching With Proxies Enabled in Netscape or Internet Explorer

If you use Netscape or Internet Explorer with proxies enabled manually, you can speed up search significantly by modifying your proxy information.

In Netscape 4, perform the following steps to modify your proxy information:

Select Edit --> Preferences.
Double-click Advanced in the Category tree.
Click Proxies in the Advanced sub-tree.
Click View at the Manual Proxy Configuration selection.
In the Exceptions...Do not use proxy servers for domains beginning with box, type
```
localhost:49213
```
If you have other entries here, separate them with commas.
Click OK until all dialog boxes are closed.

In Internet Explorer 4, perform the following steps to modify your proxy configuration:

Select View --> Internet Options.
Select the Connections tab.
Select the Bypass proxy server for local addresses box. This check box is available only if you are using a proxy or socks connection and you have selected the Use a proxy server box.
Click on Advanced.
In the Exceptions...Do not use proxy server for addresses beginning with box, type
```
localhost:49213
```
Click OK until all dialog boxes are closed.

In Internet Explorer 5, perform the following steps to modify your proxy configuration:

Select Tools --> Internet Options.
Select the Connections tab.
If you are connected to a Local Area Network (LAN), click on LAN Settings. If you use Dial-Up Networking, click on Settings.
Select the Bypass proxy server for local addresses box. This check box is available only if you are using a proxy or socks connection and you have selected the Use a proxy server box.
Click on Advanced.
In the Exceptions...Do not use proxy server for addresses beginning with box, type
```
localhost:49213
```
Click OK until all dialog boxes are closed.

Searching with a Laptop on Windows 9x

If you use a laptop that is normally connected to a LAN as a disconnected development platform, you may run into difficulty searching the DB2 product documentation. To search successfully, you need to disable your nameserver IP address in your TCP/IP configuration. In other words, you need two separate TCP/IP configurations, one for connected operations and another for disconnected ones.

Windows 9x only allows you to have a single TCP/IP configuration. However, there are shareware utilities available on the internet that let you specify more than one setting, and then change them according to your connection status. TCPSwitch is one of these programs.

Uninstalling NetQuestion on Windows 32-bit Operating Systems

Before uninstalling NetQuestion, make sure the search server is stopped. For information on how to stop the search server, see Solving Search Problems.

NetQuestion is normally uninstalled when you uninstall DB2 Universal Database. If NetQuestion is still present after properly uninstalling DB2 and rebooting your system, go to Diagnosing NetQuestion Uninstall Problems diagnose and fix the problem.

Diagnosing NetQuestion Uninstall Problems

If NetQuestion is not uninstalled after properly uninstalling DB2 and rebooting your system, it could mean that DB2 or other IBM products are still registered with NetQuestion. To determine which products are still registered with NetQuestion, issue one of the following commands:

   imndomap -a            //for SBCS
   imqdomap -a            //for DBCS

If this command lists no indexes, go to Manually Uninstalling NetQuestion on Windows 32-bit operating systems.

If this command lists indexes that do not belong to DB2 Universal Database (that is, the index names begin with something other than DB2), other products on your system are using NetQuestion. In this case you cannot remove NetQuestion.

If the list contains any of the DB2 index file names (DB2S71xx or DB2C71xx), DB2 could not unregister the indexes therefore causing the NetQuestion uninstall to fail. This usually occurs if DB2 was incorrectly uninstalled. In this case, you need to manually unregister the indexes one at a time by performing the following steps:

Issue one of these commands to ensure that the search server is running:

   imnss start server         //for SBCS
   imqss -start dbcshelp      //for DBCS

Issue one of these commands for each of the index files:
```
   imndomap -d index_name       //for SBCS
   imqdomap -d index_name       //for DBCS
```
where index_name is the name of one of the indexes returned by the imndomap -a or imqdomap -a command.
Issue one of these commands for each of the index files:
```
   imnixdel index_name        //for SBCS
   imqixdel index_name        //for DBCS
```
where index_name is the name of one of the indexes returned by the imndomap -a or imqdomap -a command.

Stop the search server:

   imnss stop server           //for SBCS
   imqss -stop dbcshelp        //for DBCS

Issue the imndomap -a or imqdomap -a command to verify that there are no DB2 indexes remaining. If there are, please contact IBM service.
Issue one of following commands to verify that no other indexes are active.
```
   nqcounti netq_dir  //for SBCS
   tmcounti netq_dir  //for DBCS
 
```
where netq_dir is the fully qualified path under which NetQuestion is installed. See Locating the NetQuestion Installation Directory if you do not know the directory under which NetQuestion is installed.
If the nqcounti or tmcounti command return data that indicates one or more indexes are still active, NetQuestion cannot be removed because other IBM products are still registered. Please contact IBM service for assistance.
If the nqcounti or tmcounti command return data that indicate no indexes are active, go to Manually Uninstalling NetQuestion on Windows 32-bit operating systems.

Manually Uninstalling NetQuestion on Windows 32-bit operating systems

If the nqcounti or tmcounti command does not list any active indices, you can try removing NetQuestion manually by performing the following steps:

From a command prompt, enter the uninstnq command.
Remove the registry entry \\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\NetQuestion.
Remove the NetQuestion installation directory. For example, if you installed NetQuestion on the C:\ drive on Windows NT, remove the c:\imnnq_nt directory.
Remove the environment variables IMNINST and IMNINSTSRV, and remove the NetQuestion installation path from the PATH environment variable.

If you still can not uninstall NetQuestion, call IBM service for assistance.

Rebooting After Uninstalling NetQuestion

After a DB2 Universal Database uninstall, it is very important to reboot before performing another DB2 installation. Some NetQuestion DLLs can be held by the operating system and are not removed until the next reboot. If a NetQuestion install happens before the reboot, the newly installed NetQuestion DLLs will be deleted on the next reboot, rendering NetQuestion unusable.

[ Top of Page | Previous Page | Next Page ]

Step 1.	Edit the `httpd.cnf` file in the NetQuestion directory and change the port number to one you know is available, preferably one above 49000.
Step 2.	Determine where your `db2path` is by entering the db2set db2path command.
Step 3.	Go to the `db2path/doc/html` directory and use a text editor to edit the `index.htm` file. In the line with the <form> tag, change the value for localhost:49213 to reflect the port number you selected in step 1.
Step 4.	Stop and re-start the search server. To stop the search server, click on Start --> Programs --> IBM DB2 --> Stop HTML Search Server. To start the search server, click on Start --> Programs --> DB2 for Windows --> Start HTML Search Server.