Extracted Portion of DB2/2 RELEASE.TXT File ===================================================== 4.0 HTML SEARCH SERVER FOR OS/2: SEARCHING HTML DOCUMENTATION IBM DB2 Universal Database (DB2 UDB) online documentation comes with an HTML search server to help you find information. These release notes describe the setup and use of the search system on OS/2. 4.1 INSTALLING THE HTML SEARCH SYSTEM ON OS/2 4.1.1 PREREQUISITES FOR THE SEARCH SYSTEM ON OS/2 You must have TCP/IP Version 3 or higher installed on your machine. OS/2 Warp V4 is recommended because it has the appropriate level of TCP/IP. OS/2 Warp V3 Internet Access Kit (IAK) will also work if you set it up for local loopback and if you install the latest FixPak. You need a browser such as Netscape 2.02 for OS/2. If a Netscape browser is not available for your language, use Web Explorer 1.1 or higher. Ensure you turn off proxy handling for localhost in the browser you use. If you are installing DB2 UDB 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. 4.1.2 CONFIGURING TCP/IP ON OS/2 The search server will function with or without a network adapter installed as long as TCP/IP local loopback and localhost are enabled on your system. To enable local loopback: 1. Open OS/2 TCP/IP folder. 2. Open the TCP/IP Configuration notebook. 3. View the Network page. 4. In the "Interface to Configure" list box, highlight "loopback interface". 5. If the "Enable interface" check box is not selected, select it now. 6. Verify that the "IP address" is 127.0.0.1 and "Subnet Mask" is empty. To enable localhost on your system: 1. To check whether or not localhost is enabled, enter "ping localhost" on an OS/2 command line. - If data is returned, localhost is enabled and you can skip steps 2 and 3 below and go directly to step 4. - If "localhost unknown" is returned, or if the command hangs, localhost is not enabled. Go to step 2. 2. If you are on a network, make sure that loopback is enabled (see "Enable local loopback", above). 3. If you are not on a network, enable localhost by performing these steps: a) Add the following line after other ifconfig lines in the MPTN\BIN\SETUP.CMD command file: ifconfig lo 127.0.0.1 NOTE: If you have OS/2 Warp with Internet Access Kit, add the line to the \STARTUP.CMD instead of the MPTN\BIN\SETUP.CMD file. If the file doesn't exist, you will have to create it. b) In the TCP/IP configuration folder, perform the following steps: 1. Go to the "Configure Name Resolution Services page" 2. In the "Hostname configuration without a Nameserver" table, add an entry with "IP Address" set to 127.0.0.1 and "Hostname" set to localhost. NOTE: If you have a hostname for your machine on the "Configure LAN Name Resolution Services" page, you must add this name as an alias when you set the IP Address 127.0.0.1 to localhost. 3. Select the "Look through HOSTS list before going to nameserver" list box. NOTE: This step tells OS/2 that when it is looking for a host, such as localhost, it should use the host address found on your machine rather than checking the nameserver. If the host is not defined on your machine, OS/2 continues looking for the host by using the nameserver you configured. 4. Close TCP/IP Configuration and reboot the system. 5. You should be able to ping localhost without being connected to any network. 4. Verify that your hostname is correct. On an OS/2 command line, enter "hostname". The hostname returned should match the one listed in the TCPIP Configuration notebook on the Hostnames page and it must be less than 32 characters. If the hostname deviates from these conditions, correct it on the Hostnames page. Then correct it in CONFIG.SYS (SET HOSTNAME=), if necessary. Reboot after you make the necessary changes. 4.1.3 VERIFYING TCP/IP CONFIGURATION Click the "Start HTML Search Server" icon, which is located in the DB2 for OS/2 folder. If an error message appears, TCP/IP is not configured properly. Follow the instructions in "2.2 Configuring TCP/IP on OS/2" to make sure that TCP/IP is correctly configured. Reboot OS/2 if you change any settings. 4.1.4 LOCATING THE SEARCH SYSTEM DIRECTORY The search system is stored in its own directory because it may be used by other products. For example, if you installed DB2 UDB along with the search system on drive G, and later you installed VisualAge for Java on drive H, only one search system is installed -- the one that came first. Some instructions in this document require you to specify the location of this directory. To locate this directory enter this command on an OS/2 command line: echo %IMNNLPSSRV% 4.1.5 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 can change the search server port with the following steps: 1. Edit the HTTPD.CNF file in the search system directory and change the port number to one you know is available, preferably above 49000. 2. Go to the DB2 UDB directory and in the %DB2PATH%/doc/html directory, use a text editor to edit the DB2SRCH.HTM file. Change the following line to the port you selected in the previous step:
where: * is D for DBCS and S for SBCS xx is a two-character identifier for the language in which the documentation is written 49213 is the new port for localhost 3. Stop and start the search server by double-clicking on the icons in the DB2 for OS/2 folder. 4.1.6 DIAGNOSING SEARCH SERVER INSTALL ERRORS If you received error messages while installing the search server, enter the following command from an OS/2 command line and follow the instructions that it returns: SNIFFLE /P Make sure you reboot your system after you're done. 4.2 USING THE HTML SEARCH SYSTEM 4.2.1 STARTING AND STOPPING THE SEARCH SERVER After you install the search system, it will start automatically after you reboot. If the search server starts without any errors but you encounter the following error message in your browser, click the "Stop HTML Search Server" icon, then click the "Start HTML Search Server" icon. A network error occurred: unable to connect to server. The server may be down or unreachable. Try connecting again later. After you have finished searching, stop the search server to reclaim the memory it used. To stop it, double-click the "Stop HTML Search Server" icon in the DB2 for OS/2 folder. 4.2.2 SEARCHING WHILE DISCONNECTED FROM THE NETWORK If you are not on a network (for example, if you are using a laptop computer and are temporarily away from a LAN connection), you have to enable localhost to search the documentation. The instructions for doing this task are described in step 3 in section "2.2 Configuring TCP/IP on OS/2". 4.2.3 FILE NOT FOUND ERRORS The search system searches predefined indexes. All of these indexes are installed with the search system, regardless of the DB2 UDB products you install. Therefore, when you conduct a search, some of the results might return a "File not found" error because they pertain to a product that is not installed on your system. 4.2.4 IF SEARCH DOES NOT WORK (ERROR 500 WHEN TRYING TO SEARCH) If you installed the search server but you get an error when you try to search the documentation, check the following items: 1. Check that the search system was properly installed. The environment variable IMNNLPSSRV should point to the search system directory (See "4.1.4 Locating the Search System Directory"). 2. The search system directory should contain these files: - A DB2SRSxx.EXE or DB2SRDxx.EXE executable file (the former is for SBCS documents, the latter is for DBCS documents). The xx is a two-character identifier of the language in which the documents are written. For example, DB2SRSEN.EXE is the executable for English language SBCS documents; DB2SRDCN is for S. Chinese DBCS documents. - DB2HEAD.HTM and DB2FOOT.HTM If these files are not present, run DB2NETQ.CMD to set up index registration and copy the files to the search system directory. 3. The search system should be registered with product documentation. Invoke this command to list all of the documentation that is registered with the search system: NQMAP -A The documentation for DB2 UDB is called DB2ADMxx, DB2APDxx, or DB2CONxx, where xx is a two-character identifier of the language in which the documents are written. One or more of these names should appear in the list of names that NQMAP returns. If the files are not there, either TCP/IP is incorrectly installed or the indexes are corrupt. Use SNIFFLE /P to fix the former, and reinstall the documentation to fix the latter. 4.2.5 ERROR DETECTED WHEN STARTING THE SEARCH SERVICE If you encounter this error: EHS0410: An error was detected when starting the search service. Stop the service and start it again. Press Enter to continue... (Sometimes the error is EHS0411 but the text is the same. This message comes up on a full black screen.) ...then your hostname might have changed since doing the install and you have to record it again. Go into the NetQuestion directory and enter: type netq.cfg to see what hostname NetQuestion is using. If you have changed the hostname, for example while configuring DHCP and DDNS, enter: netqinit Example: netqinit d:\netqos2\data 4.3 UNINSTALLING THE HTML SEARCH SYSTEM After you uninstall DB2 for OS/2, the search system is left on your hard drive. Run UNINSTNQ.CMD to remove it. 4.3.1 PROBLEMS UNINSTALLING THE SEARCH SYSTEM ON OS/2 If you ran UNINSTNQ.CMD and the search system does not uninstall, the cause may be: -TCP/IP was not configured properly. -DB2 UDB or another product is using the search system so it cannot be removed. 1.Follow the instructions in section "2.2 Configuring TCP/IP for OS/2" to ensure that TCP/IP is configured properly and search server is initialized with a properly configured TCP/IP setup. Make sure you reboot the system if you make any changes to the configuration. 2.To determine which products are still registered with the search system, issue the following command: NQMAP -A If this command returns no indexes, skip to step 6. If the list contains indexes that do not belong to DB2 UDB (that is, their names begin with something other than "DB2"), you cannot remove the search server. If it contains any of the DB2 index file names (DB2ADMxx, DB2APDxx, DB2CONxx), DB2 UDB could not unregister the indexes therefore causing the search system uninstall to fail. This occurs if DB2 UDB was incorrectly uninstalled (for example, the SQLLIB folder was deleted). In this case, you have to manually unregister the indexes and remove the search system directory using the following steps: 1. Issue this command to ensure that the search server is running: NETQ START SERVER //for SBCS IMQSS.EXE -START DBCSHELP //for DBCS 2. Issue this command for each of the index files: NQMAP -D 3. Issue this command for each of the index files: NQDELET //for SBCS TMDELET //for DBCS 4. Stop the search server: NETQ STOP SERVER //for SBCS IMQSS.EXE -STOP DBCSHELP //for DBCS 5. Issue "NQMAP -A" and verify that there are no DB2 indexes (DB2xxxxx) remaining. If there are, please contact IBM service. 6. Issue the following command to verify that no other indexes are active. NQCOUNTI //for SBCS TMCOUNTI //for DBCS NOTE: See "4.1.4 Locating the Search System Directory" if you do not know where it is installed. a)If this command returns data that indicates one or more indexes are still active, the search system cannot be removed because other products are still registered. Do not perform the remaining steps. b)If the search system returns "0 indices active", run UNINSTNQ.CMD. (Ignore this message: "SYS0016: The directory cannot be removed".) Verify that the search system directory has been removed. If it is still there, call IBM service. 7. After the UNINSTNQ.CMD completes, perform the following steps: a) Restore CONFIG.SYS from a backup that was created during install. NOTE: Install creates numbered backups, of the form config.xyz, where xyz is the first available number from 000 to 100. The backups will have the time and date stamp of the time of the install. There were two backups created during install: one for the DB2 UDB install, one for the search system install. -To remove only search system settings, use the second backup. -To remove both DB2 UDB and search system settings, use the first backup. b) Remove the search system's directory and all its subtrees. 1. Go to the %TMP%/NETQ directory. 2. Delete any files that remain in the NETQ directory. 3. Delete the NETQ directory. 4. Reboot. 5.0 HTML SEARCH SERVER FOR WINDOWS NT, WINDOWS 95, AND WINDOWS 98: SEARCHING HTML DOCUMENTATION IBM DB2 Universal Database (DB2 UDB) online documentation comes with an HTML search system to help you find information. These release notes describe the setup and use of the search system on Windows NT, Windows 95, and Windows 98. The search system consists of a search engine and a search server. The search system is stored in its own directory because it may be used by other products. 5.0.1 RESTRICTIONS ON USE This search system does not support Windows 3.1. This search system is not enabled for Thin Clients. If you attempt to search the documentation, you will receive a network error. 5.1 INSTALLING THE HTML SEARCH SYSTEM ON WINDOWS NT, WINDOWS 95, AND WINDOWS 98 5.1.1 PREREQUISITES FOR THE SEARCH SYSTEM The following prerequisites are required: 1. On Windows NT 4.0, for best results you should have installed Service Pack 3. For information see http://www.microsoft.com/ntserver/info/servicepack3.htm. 2. You need a browser, such as Netscape 3.0. Ensure you turn off proxy handling for localhost in the browser you use. 3. You must have TCP/IP Version 3 or higher installed on your machine. It must be installed and configured in order for the DB2 UDB search system to function properly. For Windows 95, 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. - Your LAN DNS must resolve "localhost" to 127.0.0.1. - You cannot run disconnected with a LAN adapter configuration. 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 Control Panel. The overriding of the properties will only take place so long as the Dial-Up Adapter TCP/IP properties are configured as above. Enabling the DNS in the Dial-Up Adapter TCP/IP properties or setting an IP address in the Dial-Up Adapter TCP/IP properties will interfere with the Dial-Up networking configuration for the ISP and must be avoided. For Windows NT 4.0, either of the TCP/IP configurations detailed above will work. If you are running standalone, you can also enable the MS Loopback Adapter without the other two adapters. 5.1.2 STOP ANY PREVIOUSLY INSTALLED VERSION OF THE SEARCH SYSTEM If the search system was previously installed by another product (for example, VisualAge for Java), the search server must be stopped. To stop the search server, click on "Stop HTML Search Server" in the DB2 menu item of the Start Menu. 5.1.3 LOCATING THE SEARCH SYSTEM DIRECTORY The search system is stored in its own directory because it may be used by other products. For example, if you installed DB2 UDB along with the search system on drive G, and later you installed VisualAge for Java on drive H, only one search system is installed -- the one that came first. Some instructions in this document require you to specify the location of this directory. To locate this directory use this command: echo %IMNINSTSRV% 5.1.4 CHANGING TO A DIFFERENT 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 can change the search server port with the following steps: 1. Edit the HTTPD.CNF file in the search system directory and change the port number to one you know is available, preferably above 49000. 2. Determine where is by issuing the following command: DB2SET DB2PATH 3. Go to the DB2 UDB directory and in the /doc/html directory, use a text editor to edit the DB2SRCH.HTM file. Change the following line to the port you selected in the previous step: where: * is D for DBCS and S for SBCS xx is a two-character identifier for the language in which the documentation is written 49213 is the new port for localhost 4. Stop and start the search server. To stop the search server, click on "Stop HTML Search Server" in the DB2 menu item of the Start Menu. To start the search server, click on "Start HTML Search Server" in the DB2 menu item of the Start Menu. 5.1.5 INSTALLING DB2 UDB ON A LAN-CONNECTED DRIVE (WINDOWS 95) If you install DB2 UDB on a LAN-connected drive on Windows 95 and the drive does not get reconnected before AUTOEXEC.BAT is run on Windows 95, the search system will not be able to have its environment variables set. The search system sets environment variables through a batch file (IMNENV.BAT) that resides in the search system directory (for example, (F:\IMNNQ_95). To bypass this problem, copy IMNENV.BAT from the search system directory to another drive/directory that is connected before AUTOEXEC.BAT is executed. Then modify AUTOEXEC.BAT to call this batch file on startup. 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 5.1.6 DIAGNOSING SEARCH SERVER INSTALL ERRORS If during DB2 UDB install you encounter a failed search server installation or initialization, the DB2 UDB install will proceed to completion. The following will assist in diagnosing what happened and what to do: - Look in \imnnq\install directory (where 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 is 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 \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 XXX.EXE DOES NOT EXIST, the search system executables could not be found. Try rerunning the search system install/initialization program again. See section "4.2.4 If Search Does Not Work (ERROR 500 when trying to search)". 5.2 USING THE HTML SEARCH SYSTEM 5.2.1 STARTING AND STOPPING THE SERVER After you install the search system, it will start automatically after you reboot. If the search server starts without any errors but you encounter the following error message in your browser, click "Stop HTML Search Server", then click on "Start HTML Search Server" in the DB2 menu item of the Start Menu. A network error occurred: unable to connect to server. The server may be down or unreachable. Try connecting again later. After you have finished searching, stop the search server to reclaim the memory it used. To stop it, click on "Stop HTML Search Server" in the DB2 menu item of the Start Menu. 5.2.2 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 3: ---------------- 1. Select Options - Network Preferences. 2. Click the Proxies tab. 3. Click View at the Manual Proxy Configuration selection. 4. In the "No proxies for" box, type: localhost:49213 If you have other entries here, separate them with commas. 5. Click OK to close the Manual Proxy Configuration window. 6. Click OK to exit the Preferences Window. In Netscape 4 (Communicator) ---------------------------- 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. 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. 6. Click OK to close the Manual Proxy Configuration window. 7. Click OK to exit the Preferences Window. In Internet Explorer 3 ---------------------------- 1. Select View - Options. 2. Select Connection. 3. 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. 4. Select the "Do not use proxy server for local (intranet) addresses" box. 5. Click OK to exit the Options Window. In Internet Explorer 4 --------------------------------------- 1. Select View... Internet Options 2. Select the Connection tab 3. Select the "Bypass proxy server for local (Intranet) access" check box. NOTE: this check box is only available if you are using a proxy or socks connection and have selected the "Access the Internet Using a Proxy Server" check box 4. Select the "Advanced" Button 5. Type: localhost:49213 in the "Exceptions... Do not use proxy servers for addresses beginning with" box. If you have other entries here, separate the new entry with a semi-colon. 6. Select OK, then OK to exit the Options Tab 5.2.3 SEARCHING WITH A LAPTOP ON WINDOWS 95 Nameservers: ------------ If you use a laptop that is normally connected to a LAN as a disconnected development platform, you may run into difficulty searching. 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. Best fix for multiple TCP/IP configurations in Windows 95: ---------------------------------------------------------- Windows 95 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 (connected or disconnected from a LAN). TCPSwitch is one of these programs. Socks servers and proxies: -------------------------- If you are using Netscape 3, and you dial-in to a secure site to access the internet with a proxy or socks server, you will need to delete these settings in Netscape before you can search. This is a bug with Netscape 3--Netscape Communicator's "direct connect" setting should fix this. 5.2.4 IF SEARCH DOES NOT WORK (ERROR 500 WHEN TRYING TO SEARCH) If the product installation worked, but searching does not work, try the following steps: 1. Check that the search system was properly installed. The environment variables IMNINST and IMNINSTSRV should be set and IMNINSTSRV should point to the search system directory (see "5.1.3 Locating the Search System Directory"). 2. The search system directory should contain these files: - A DB2SRSxx or DB2SRDxx executable file (the former is for SBCS documents, the latter is for DBCS documents). The xx is a two-character identifier of the language in which the documents are written. For example, DB2SRSEN is the executable for English language SBCS documents; DB2SRDCN is for S. Chinese DBCS documents. - DB2HEAD.HTM and DB2FOOT.HTM 3. Ensure that the search system is registered with product documentation. Invoke this command to list all of the documentation that is registered with the search system: NQMAP -A //for SBCS TMMAP -A //for DBCS The documentation for DB2 UDB is called DB2ADMxx, DB2APDxx, or DB2CONxx, where xx is a two-character identifier of the language in which the documents are written. One or more of these names should appear in the list of names that NQMAP (or TMMAP) returns. With the list of indexes the NQMAP (or TMMAP) command provides, you can get additional details on each index with the following command: IMNIXSTA //for SBCS IMQIXSTA //for SBCS This command provides details such as the status of the index and the number of documents in the index. If any of the above conditions are not true, you can rerun the DB2 UDB product installation program. If the only condition that is not true is that the files DB2SRCH.EXE, DB2HEAD.HTM and DB2FOOT.HTM are missing, then you can just copy them over from the directory \misc into search system's directory, (for example, E:\IMNNQ_NT). The product installation program will rerun the search server's installation and initialization. 5.2.5 FILE NOT FOUND ERRORS The search system searches predefined indexes. All of these indexes are installed with the search system, regardless of the DB2 UDB products you install. Therefore, when you conduct a search, some of the results might return a "File not found" error because they pertain to either a product that is not installed on your system, or, a document that you chose not to install during installation. 5.2.6 ERROR DETECTED WHEN STARTING THE SEARCH SERVICE If you encounter this error: EHS0410: An error was detected when starting the search service. Stop the service and start it again. Press Enter to continue... (Sometimes the error is EHS0411 but the text is the same. This message comes up on a full black screen.) ...then your hostname might have changed since doing the install and you have to record it again. Go into the NetQuestion directory and enter: type netq.cfg to see what hostname NetQuestion is using. If you have changed the hostname, for example while configuring DHCP and DDNS, enter: netqinit Example: netqinit c:\imnnq_nt\data 5.3 UNINSTALLING THE HTML SEARCH SYSTEM Note: Before uninstalling the DB2 UDB product, the search system must be stopped. To stop the search system, click on "Stop HTML Search Server" in the DB2 menu item of the Start Menu. The search system is uninstalled with the DB2 UDB product by clicking on the "Uninstall" item in the DB2 menu item of the Start Menu. 5.3.1 IF THE SEARCH SYSTEM IS NOT UNINSTALLED FROM WINDOWS NT OR WINDOWS 95 If the search system does not get uninstalled the cause may be: -DB2 UDB or another product is using the search system so it cannot be removed. -The search system uninstall did not perform as expected. To determine which products are still registered with the search system, issue the following command: NQMAP -A //for SBCS TMMAP -A //for DBCS If this command returns no indexes, skip to step 6. If the list contains indexes that do not belong to DB2 UDB (that is, their names begin with something other than "DB2"), you cannot remove the search server. If it contains any of the DB2 index file names (DB2ADMxx, DB2APDxx, DB2CONxx), DB2 UDB could not unregister the indexes therefore causing the search system uninstall to fail. This occurs if DB2 UDB was incorrectly uninstalled (for example, the SQLLIB folder was deleted). In this case, you have to manually unregister the indexes and remove the search system directory using the following steps: 1. Issue this command to ensure that the search server is running: IMNSS START SERVER //for SBCS IMQSS.EXE -START DBCSHELP //for DBCS 2. Issue this command for each of the index files: NQMAP -D //for SBCS TMMAP -D //for DBCS 3. Issue this command for each of the index files: NQDELET //for SBCS TMDELET //for DBCS 4. Stop the search server: IMNSS STOP SERVER //for SBCS IMQSS.EXE -STOP DBCSHELP //for DBCS 5. Issue "NQMAP -A" (or "TMMAP -A") and verify that there are no DB2 indexes (DB2xxxxx) remaining. If there are, please contact IBM service. 6. Issue the following command to verify that no other indexes are active. NQCOUNTI //for SBCS TMCOUNTI //for DBCS NOTE: See "5.1.3 Locating the Search System Directory" if you do not know where it is installed. a)If this command returns data that indicates one or more indexes are still active, the search system cannot be removed because other products are still registered. Do not perform the remaining steps. b)If the search system returns "0 indices active", run UNINSTNQ.EXE. If the search system still does not uninstall, you can try removing the product manually: - Remove the registry entries that are under \\HKEY_LOCAL_MACHINE\SOFTWARE\IBM\NetQuestion. Remove this entry including all its subtrees - Remove the search system's directory and all its subtrees (for example, D:\IMNNQ_NT) - Remove the environment variables IMNINST and IMNINSTSRV and remove the search system path from the PATH environment variable. If you still can't uninstall the search system, call IBM service. 5.3.2 REBOOTING AFTER UNINSTALLING THE PRODUCT After a DB2 UDB uninstall, it is very important to reboot before doing another install. The reason is that some search system DLLs can be held by the operating system and are not removed until the next reboot. If a a search system install happens before the reboot, the newly installed search system DLLs will be deleted on the next reboot, rendering the search system unusable.