A catalog server refers to a combination of where the database resides and the communications protocol used.
IBM uses the term "node" for the location of remote database servers; Host Compatibility Option refers to them as "servers."
You can use the GUI tool provided by Host Compatibility Option or one of the utilities provided by IBM such as Client Configuration Assistant to use remote databases for application development. However, you first need to catalog both the server and the database (see the chapter Catalog Database for more details on how to catalog databases).
The Catalog Server tool (see Figure 8-1) appears when you click HCO > Catalog Server on the Tools menu.
Figure 8-1: Catalog Server Tool
The following elements make up the Catalog Server tool:
The following list shows the buttons in the toolbar and the functions that they invoke:
|Display the Catalog Remote Server window (see Figure 8-2) to enter information required to catalog a remote database server.|
|Uncatalog a server. To enable the uncatalog function, you must select a server from the list box. This function only affects servers cataloged on your PC.|
|Switch to Catalog Database tool. See the chapter Catalog Database for more details.|
|Display the online HCO User's Guide,which is a hypertext file that describes how the Catalog Server tool works.|
The menu bar is an alternate way of invoking Catalog Server functions. The menu bar is composed of two menus: Server and Help.
To run a command or to exit the tool, select the server menu. You can also display this menu by right-clicking on the Catalog Server window (see Figure 8-1).
|Catalog remote server||Display the Catalog Remote Server window (see Figure 8-2) to enter information required to catalog a remote database server.|
|Uncatalog server||Uncatalog a server. Function is disabled until a server has been selected from list box. This function only affects servers cataloged on your PC.|
|List databases||Switch to Catalog Database tool to see the cataloged databases on your PC. See the chapter Catalog Database for more details.|
|Exit||Exit Catalog Server tool.|
To catalog a remote database server, either click Catalog or select Catalog remote server from Server menu. A window similar to the Catalog Remote Server window appears (see Figure 8-2).
Figure 8-2: Catalog Remote Server Window
When you select one of the protocol radio buttons listed, entry fields for that protocol are then displayed in the Protocol Settings group box. In the example above, TCP/IP has been selected.
In the entry fields provide the following information and then click Catalog.
|Server Name||A unique name that you give the remote database server where the database is located.|
|Comment||A brief description to use to identify the server (30 characters maximum). Entry is optional.|
|Protocol - TCP/IP||Select this radio button if you want to use TCP/IP communications protocol. When you select this button, entry fields for TCP/IP parameters are displayed in the Protocol Settings box (see Figure 8-2).|
|Protocol - NET BIOS||Select this radio button if you want to use the NETBIOS communications protocol. When you select this button, entry fields for NETBIOS parameters are displayed in the Protocol Settings box (see Figure 8-2).|
|Protocol - IPX/SPX||Select this radio button if you want to use IPX/SPX communications protocol. The Protocol IPX/SPX Window is then displayed.|
|Protocol - APPC||Select this radio button if you want to use APPC communications protocol. When you select this button, entry fields for APPC parameters are displayed in the Protocol Settings box (see Figure 8-2).|
|Host Name||The host-name of the server where the target database resides. The host-name is the name of the server that is known to the TCP/IP network. Maximum length is 255 characters.|
|Service Name||Either the service-name of the
database manager on the remote database server, or the port number
associated with that service-name.
If it is the service-name, it must match the service-name specified in the database manager configuration file on the remote server (svcename), and must be specified with the same port number in both the local and the remote TCP/IP services files. See IBM DB2 Command Reference for more details on displaying Database Manager Configuration details
If it is the port number, it must match the port number associated with the service-name of the remote node. That service-name does not have to be specified in the local TCP/IP services file. The value of servicename is used as a key to search the local services file for the associated port number. If a matching entry is not found, and servicename is numeric, the value itself is interpreted as the port number.
Maximum length is 14 characters. This parameter is case sensitive.
|Server NName||The NName parameter in the Database Manager configuration of the remote database server. You must know this name to connect successfully . See IBM DB2 Command Reference for more details on displaying Database Manager Configuration details.|
|Adapter||Specifies the local logical outgoing LAN Adapter number.|
|Fileserver||Name of the NetWare file server where the Internet work address of the database manager instance is registered. The Internet work address is stored in the bindery at the NetWare file server, and is accessed using object-name.|
|Objectname||Name of the database manager instance stored in the bindery of the NetWare file server. Each database manager instance registered at one NetWare file server must be represented by a unique object-name. It is recommended that each database manager instance on the network be represented by a unique object-name.|
|Destination Name||Specifies the symbolic destination-name of the remote partner node. The name APPC corresponds to an entry in the CPI Communications side information table that contains the necessary information for the client to set up an APPC connection to the server (partner LU-name, mode-name, partner TP-name). Maximum length is 8 characters.|
|Security||Select one of the following:|
|PROGRAM||Specifies that both a user-name and a password are to be included in the allocation request sent to the partner LU.|
|NONE||Specifies that no security information is to be included in the allocation request sent to the partner LU.|
|SAME||Specifies that a user-name is to be included in the allocation request sent to the partner LU, together with an indicator that the user-name has been "already verified". The partner must be configured to accept "already verified" security.|
Contact your network administrator for further details as to what these values should be.
You need one of the following authorization levels to be able to execute this function:
If you make a mistake cataloging the server you can uncatalog it from this tool by doing the following:
Copyright © 2001 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.