Provided your system meets the installation prerequisites detailed in NetQuestion Prerequisites, NetQuestion is usually installed automatically whenever DB2 product documentation is installed, and the search server is started whenever your OS/2 system is booted. To search the DB2 product documentation all you have to do is open the HTML search form (db2srch.htm, located in x:\sqllib\doc\html where x:\ is the DB2 install drive) in a browser such as Netscape 2.02, enter your search criteria, and click on the Search button.
The following prerequisites are required to install and work with NetQuestion:
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 on your system:
step 1. | Open the OS/2 TCP/IP folder. |
step 2. | Open the TCP/IP Configuration notebook. |
step 3. | View the Network page. |
step 4. | In the Interface to Configure list box, highlight loopback interface. |
step 5. | If the Enable interface check box is not selected, select it now. |
step 6. | Verify that the IP address is 127.0.0.1 and Subnet Mask is empty.
|
To enable localhost on your system:
step 1. | To check if localhost is enabled, enter the ping localhost command.
| ||||
step 2. | If you are on a network, make sure that loopback is enabled. To enable local loopback see Enabling Local Loopback. | ||||
step 3. | If you are not on a network, enable localhost by performing these steps:
| ||||
step 4. | Verify that your hostname is correct. On an OS/2 command line, enter the hostname command. 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. | ||||
step 5. | Verify that your hostname is set properly in CONFIG.SYS. You should see a line similar to the following: SET HOSTNAME=<correct_name> where <correct_name> is the value returned by the hostname command. If this is not the case, make the necessary changes and reboot your system when you are finished.
|
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 Configuring TCP/IP to make sure that TCP/IP is correctly configured. Reboot OS/2 if you change any settings.
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 this directory. To locate this directory enter one of the following commands:
echo %IMNINSTSRV% //for SBCS versions echo %IMQINSTSRV% //for DBCS versions
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 number by performing the following steps:
If you received error messages while installing NetQuestion, enter the SNIFFLE /P command and follow the instructions that it returns
Make sure you reboot your system after you are finished correcting any NetQuestion install errors.
After you install NetQuestion, the search server will start automatically after you reboot.
If the search server starts without any errors but you encounter the following error message when you attempt to search the DB2 product documentation:
A network error occurred: unable to connect to server. The server may be down or unreachable. Try connecting again later.
then stop and re-start the search server by clicking on the appropriate icons in the DB2 for OS/2 folder.
After you have finished searching, stop the search server to reclaim the memory it used.
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. For more information on enabling localhost, see Configuring TCP/IP.
NetQuestion searches predefined indexes (and not the actual HTML documentation installed with your DB2 product) and displays a list of ranked hits in a Search Results page. All of these indexes are installed with NetQuestion, regardless of the DB2 products you install.
However, depending on the DB2 product you installed, some of the HTML documentation may not be present. Therefore, the links generated from the predefined indexes may, if followed, return "File not found" errors.
For example, you install DB2 Universal Database Personal Edition with product documentation selected. You load the DB2 search page, select the Application Development index, and search for "Embedded SQL". Most of the hits returned in the Search Results page will (if you "mouse over" the links) point to URLs like FILE:///C:\SQLLIB\DOC\HTML\db2a0/db2a093.htm, which is a file in the HTML version of the Application Development Guide. However, this book (db2a0) is not installed with DB2 Universal Database Personal Edition. Therefore, the links in the Search Results page will, if followed, produce "File not found" errors.
You can determine which HTML books are installed by opening the DB2 for OS/2 folder, double-clicking on Information Center, and selecting the Books tab. You can also look in <installation drive>:\sqllib\doc\html and comparing the five-character folder names (such as db2s0 and db2h1) to the list of books in the "How the DB2 Library is Structured" appendix in your Quick Beginnings manual.
If you installed NetQuestion but you get an Error 500 when you try to search the documentation, perform the following steps to diagnose and fix the problem:
step 1. | Check that NetQuestion was properly installed. The environment variable IMNNLPSSRV should point to the NetQuestion directory. For information on locating the NetQuestion directory see Locating the NetQuestion Directory. |
step 2. | The NetQuestion directory should contain these files:
|
step 3. | Ensure that the product documentation indexes are registered with NetQuestion. To list all registered indexes enter one of the following commands: nqmap -a //for SBCS tmmap -a //for DBCS The documentation indexes for DB2 is called DB2SR6xx or DB2CC6xx 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 one of the following commands: imnixsta <index_name> //for SBCS imqixsta <index_name> //for DBCS where <index_name> is the name of one of the indexes returned by the nqmap -a (or tmmap -a) command. The imnixsta (or imqixsta) command provides details such as the status of the index and the number of documents in the index. If any of the above commands reveal an error, either TCP/IP is incorrectly installed or the NetQuestion indexes are corrupt. Use the SNIFFLE /P command to diagnose and fix TCP/IP errors, and reinstall the documentation to fix index corruption problems.
|
If you encounter this error:
EHS0410 (or EHS0411): An error was detected when starting the search service. Stop the service and start it again. Press Enter to continue...
your hostname might have changed since doing the install, and you have to record it again. From a command prompt, switch to the NetQuestion installation directory and enter:
type netq.cfg
to see which hostname NetQuestion is using. If you have changed the hostname, for example while configuring DHCP and DDNS, enter:
netqinit <data-path>
where <data_path> is the data directory under the NetQuestion installation directory. For example, if you installed NetQuestion on the D: drive, <data_path> would resolve to d:\netqos2\data.
Before uninstalling NetQuestion, make sure the search server is stopped. For information on how to stop the search server, see Starting and Stopping the Search Server.
To uninstall NetQuestion, enter the following command:
uninstnq.cmd
If NetQuestion is still present after executing this command, continue reading this section to diagnose and fix the problem.
If you executed uninstnq.cmd and NetQuestion does not uninstall, the cause may be one of the following:
To determine which products are still registered with the search system, issue one of the following commands:
nqmap -a //for SBCS tmmap -a //for DBCS
If this command lists no indexes, go to Manually Uninstalling NetQuestion.
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 (DB2SR6xx or DB2CC6xx), DB2 could not unregister the indexes therefore causing the NetQuestion uninstall to fail. This occurs if DB2 was incorrectly uninstalled (for example, the SQLLIB folder was deleted). In this case, you need to manually unregister the indexes one at a time by performing the following steps:
step 1. | Issue one of these commands to ensure that the search server is running: netq start server //for SBCS imqss -start dbcshelp //for DBCS |
step 2. | Issue one of these commands for each of the index files: nqmap -d <index_name> //for SBCS tmmap -d <index_name> //for DBCS where <index_name> is the name of one of the indexes returned by the nqmap -a (or tmmap -a) command. |
step 3. | Issue one of these commands for each of the index files: nqdelet <index_name> //for SBCS tmdelet <index_name> //for DBCS where <index_name> is the name of one of the indexes returned by the nqmap -a (or tmmap -a) command. |
step 4. | Stop the search server: netq stop server //for SBCS imqss -stop dbcshelp //for DBCS |
step 5. | Issue nqmap -a (or tmmap -a) and verify that there are no DB2 indexes remaining. If there are, please contact IBM service. |
step 6. | Issue the following command to verify that no other indexes are active. nqcounti <NetQuestion directory> //for SBCS tmcounti <NetQuestion directory> //for DBCS where <NetQuestion directory> is the fully qualified path under which NetQuestion is installed. See Locating the NetQuestion Directory if you do not know the directory under which NetQuestion is installed. Caution:
If the nqcounti (or tmcounti) command return data that indicate no indexes are active, go to Manually Uninstalling NetQuestion.
|
If the nqmap -a (or tmmap -a) command does not list any active indexes, you can try removing NetQuestion manually by performing the following steps:
step 1. | From a command prompt, enter uninstnq.cmd Ignore this message: "SYS0016: The directory cannot be removed." | ||
step 2. | Remove the NetQuestion directory and all of its subtrees. For example, if you installed NetQuestion on the D: drive, remove the d:\netqos2 directory. | ||
step 3. | Restore CONFIG.SYS from a backup that was created during the installation of DB2.
| ||
step 4. | Reboot your system.
|