When you install DB2 online documentation, the NetQuestion search system is
also installed. The following components make up the search
system:
To search the DB2 online information, launch the DB2 Information page in a
browser, enter your search terms, and click Search.
You may occasionally encounter an error when searching the DB2 online
information. If you do encounter a search error, try the following
troubleshooting tips:
- Is the search server running?
-
If you receive a return code 33 when you attempt to search the DB2
documentation, the NetQuestion search server is not running.
To start the search server on Windows 9x, Windows NT and Windows 2000,
click Start and go to Programs --> IBM
DB2 --> Start HTML Search Server. You can
also start the search server by entering one of the following commands:
x:\imnnq_nt\imnss start server //for SBCS
x:\imnnq_nt\imqss -start dbschelp //for DBCS
Note that the NetQuestion install directory on Windows 9x is
x:\imnnq_95.
To start the search server on OS/2, open the IBM DB2 folder and
click on the Start HTML Search Server icon. You can also
entering one of the following commands:
x:\imnnq\imnss start server //for SBCS
x:\imnnq\imqss -start dbcshelp //for DBCS
To start the search server on AIX, HP-UX and Solaris systems, enter one of
the following commands:
- On AIX
-
Enter the /usr/IMNSearch/bin/imnss -start imnhelp command for
SBCS installations. The imnss -start command can also be
executed without typing the full pathanme if /usr/bin is in your PATH.
Enter the /usr/IMNSearch/bin/imqss -start dbcshelp command for
DBCS installations. In DBCS installations, you must ensure that the
IMQCONFIGSRV and IMQCONFIGCL environment variables are set. You can set
these variables by executing the /usr/IMNSearch/bin/.
imq_env command. Again, you can execute both the imqss
-start and . imq_env commands without typing the full
pathname if /usr/bin is in your PATH.
- On HP-UX
- Enter the /sbin/rc2.d/S990IMNSearch start command for
SBCS and DBCS installations. This command will also start the
NetQuestion web server, if it is not already running.
- On Solaris
- Enter the /etc/rc2.d/S90IMNSearch start command for SBCS
and DBCS installations. This command will also start the NetQuestion
web server, if it is not already running.
To stop the search server, replace start with stop
in the above commands.
- Is the NetQuestion web server running?
-
NetQuestion comes with its own basic web server. You can also use your
own web server with NetQuestion. You should make sure that the web
server you are using is running. The following information applies to
the NetQuestion web server. To start other web servers, consult your
web server's product documentation.
On Windows NT and Windows 2000 systems, check the Task Manager to see if
the httpdl.exe process is running. If it is not
running, start it by entering the x:\imnnq_nt\httpdl -r
httpd.cnf command, where x: is your DB2
installation drive.
On OS/2, run the x:\sqllib\bin\db2netqd start command,
where x: is your DB2 installation drive The NetQuestion web server and
the search server will be started if they are not already running. You
can also run the pstat | find "httpdl" command to check if the
process is running.
On AIX, HP-UX and Solaris, enter the ps -ef | grep httpdlite
command to see if the httpdlite process is running. If it is
not running, start it by entering one of the following commands:
- On AIX
- /usr/IMNSearch/httpdlite/httpdlite -r
/etc/IMNSearch/httpdlite/httpdlite.conf
- On HP-UX
- /sbin/rc2.d/S990IMNSearch start
- On Solaris
- /etc/rc2.d/S90IMNSearch start
- Are the document indices registered with the search server?
- DB2's document indices are registered with the search server during
installation. To check if the indices are registered properly:
- Enter the imndomap -a or imqdomap -a command to
determine which indices are installed, and where they are installed.
These commands should return one or more indices with names similar to
DB2S71xx or DB2C71xx, where xx is the
two-letter language identifier of the installed documentation. If this
is not the case, re-install your DB2 product and be sure to select to install
the product documentation component.
If the indices still are not registered with the search server, you can try
to register them manually. For more information on manual index
registration, refer to your operating system's section later in this
chapter.
- Enter the imnixsta (or imqixsta for DBCS)
INDEX_NAME command, where INDEX_NAME
is one of the index names returned by the command in step 1. The output
from this command should indicate, in part, that search is available.
- DB2 indices should be located in the following directories:
x:\sqllib\doc\html //Windows and OS/2
/var/docsearch/indexes //AIX, HP-UX, and Solaris
- Is TCP/IP configured properly?
- NetQuestion uses TCP/IP for communication on all systems except on OS/2,
which uses Named Pipes (although TCP/IP is also supported). Therefore,
your system must have TCP/IP installed and configured properly, and your
system must be able to resolve localhost if you are searching documentation
installed locally. For more information on configuring TCP/IP, see your
operating system's section later in this chapter.
- Is the search CGI in the correct location, and is it named correctly?
- The DB2 search CGI must be located in a specific directory. On
Windows and OS/2 operating systems, this directory is the NetQuestion
installation direction which can be determined by entering the echo
%IMNINSTSRV% command for SBCS installations, or echo
%IMQINSTSRV% command for DBCS installations. On UNIX operating
systems, the search CGI is installed in
/var/docsearch/cgi-bin.
On Windows and OS/2 operating systems, the SBCS search CGI is named
db2srsXX.exe and the DBCS version is named
db2srdXX.exe, where XX represents the
two-letter language identifier of the installed documentation.
On UNIX operating systems, the SBCS search CGI is named
db2srsbcs and the DBCS search CGI is named
db2srdbcs. There are no language-specific NetQuestion search
CGIs on UNIX operating systems.
Also, make sure that the name of your search CGI matches the one in the
<form action="http..."> tag in the DB2
search form. For example, in the English search form on Windows or OS/2
this tag should read <form
action="http://localhost:49213/cgi-bin/db2srsen.exe"
method="POST>".
- Are the correct books or help files installed, and are they in the correct
directory?
- If you received a "File Not Found (Error 404)" message, make sure the
links on the search results page are pointing to a valid URL. If your
DB2 documentation is installed locally, all URLs should begin with
file:// . For documentation that is being served from
another computer, all URLs should begin with http:// .
- Are you using the correct search parameters?
- When you are searching for words or phrases, you should keep the following
in mind:
- To search using wildcards, use a question mark (?) for any single
character or an asterisk (*) as a placeholder for zero or more
characters.
- When using wildcards you may encounter a return code 22 in the search
results page. This means that your search request was too
complex. You should reformulate your request so that it is more
specific. For example, searching for DB* on all of the books
and online help may produce a return code 22.
- Enclose phrases in double quotes.
- To include a particular term or phrase in your search results, precede the
word or phrase with a plus sign (+). You can exclude words or phrases
from your search results by preceding them with a minus sign (-).
- Boolean operators such as AND, OR, and NOT are not supported. Use
plus or minus signs instead.
For additional platform-specific troubleshooting information, see the
following sections: