This section describes post-installation configuration information, additional troubleshooting tips, and workarounds for known issues with NetQuestion on OS/2 operating systems. It also describes how to remove NetQuestion from your system.
With the release of DB2 Version 7.1, NetQuestion no longer uses TCP/IP for communication between the browser, web server and search server. Instead, NetQuestion uses Named Pipes by default for local communication. However, if you will be using NetQuestion to search DB2 documentation in a client/server environment, you can enable it to use TCP/IP for communication. For more information on enabling NetQuestion to use TCP/IP, see Switching NetQuestion to use TCP/IP.
In addition to meeting the general installation prerequisites for DB2, he following prerequisites are required to install and work with NetQuestion:
NetQuestion in DB2 for OS/2 Version 7.1 uses Named Pipes instead of TCP/IP for local communication. This section describes how to enable NetQuestion to use TCP/IP.
| Note: | If NetQuestion is already installed on you system for use with another IBM application, such as Visual Age C++ for OS/2, it will likely already be set up to use TCP/IP for communication. In this case, when you install DB2 for OS/2 Version 7.1, the existing version of NetQuestion will be upgraded automatically but it will continue to use TCP/IP for communication so that your other NetQuestion-dependent applications continue to work properly. |
To enable NetQuestion to use TCP/IP:
If you want to switch back to communication using named pipes, repeat the above steps replacing netq.cfg with imncxpip.cfg. You can also switch communication to use unnamed pipes by replacing netq.cfg with imncxloc.cfg.
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. For more information on enabling local loopback and localhost, see Control Center Installation and Configuration.
To verify your TCP/IP configuration, open the IBM DB2 folder and double-click the Start HTML Search Server icon. If an error message appears, TCP/IP is not configured properly. Follow the instructions in Control Center Installation and Configuration to make sure that TCP/IP is correctly configured. Reboot OS/2 if you change any settings.
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 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:\imnnq\data.
If, for example, you are using a laptop computer and are temporarily away from a network connection, you must enable localhost to search the documentation. For more information on enabling localhost, see Configuring TCP/IP on OS/2.
NetQuestion is installed 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:\, the search system is only installed in one place.
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 echo %IMQINSTSRV% //for DBCS
You can also run the x:\sqllib\bin\db2netqd dir command, where x: is your DB2 installation drive.
Before uninstalling NetQuestion, make sure the search server is stopped by using the appropriate icon in the IBM DB2 folder.
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:
imndomap -a //for SBCS imqdomap -a //for DBCS
If this command lists no indices, go to Manually Uninstalling NetQuestion on OS/2.
If this command lists indices 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 indices therefore causing the NetQuestion uninstnq.cmd to fail. This usually occurs if DB2 was incorrectly uninstalled. In this case, you need to manually unregister the indices one at a time by performing the following steps:
imnss start server //for SBCS imqss -start dbcshelp //for DBCS
imndomap -d index_name //for SBCS imqdomap -d index_name //for DBCS
where index_name is the name of one of the indices returned by the imndomap -a or imqdomap -a command.
imnixdel index_name //for SBCS imqixdel index_name //for DBCS
where index_name is the name of one of the indices returned by the imndomap -a or imqdomap -a command.
imnss stop server //for SBCS imqss -stop dbcshelp //for DBCS
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 Directory if you do not know the directory under which NetQuestion is installed.
If the nqcounti or tmcounti command returns data that indicate no indices are active, go to Manually Uninstalling NetQuestion on Windows 32-bit operating systems.
If the nqcounti or tmcounti command returns data that indicate one or more indices are still active, NetQuestion cannot be removed because other products are still registered. Please contact IBM service for assistance.
If the nqcounti or tmcounti command does not list any active indices, you can try removing NetQuestion manually by performing the following steps:
uninstnq.cmd
Ignore this message: "SYS0016: The directory cannot be removed."
| Note: | DB2 install creates numbered backups of CONFIG.SYS in the form CONFIG.xyz, where xyz is the first available number from 000 to 100. The backups will have a time and date stamp corresponding to the time and date of the install. Two backups are created during any DB2 Universal Database install: one for the DB2 install, and one for the NetQuestion install. |