Specifies that you have a file containing the information required to set up a connection with the database being added.

Specifies that the discovery facility will be used to search the network for databases that can be added.

Specifies that you will enter all the information necessary to connect to the database being added.

Moves one page forward in the wizard. This button may also be disabled on some pages until all required information has been entered.

Select when you have a plug-in, the Authentication is controlled by an external GSS-API plugin.

Select to Authenticate on the server. The server accepts encrypted userids and passwords, and will encrypt the data. This operates the same way as SERVER_ENCRYPT, except the data is encrypted as well.

Starts the process that creates a database based on your specifications.

Cancels any unsaved changes that you made and closes this wizard.

Type a profile name or click [...] to search for the profile.

Displays a list of databases associated with the Profile name.

Lists the databases associated with the Profile name. Select the database that you want to add.

Specifies that the connection to the database is direct.

Specifies that the connection to the database is through a DB2 Connect gateway.

Moves one page back in the wizard.

Type a 1- to 8-character local nickname that can be used by applications running on your workstation to identify the Database.

Optional: Type a comment that can be used in conjunction with the Alias to identify the database.

Select if you are planning to use Open Database Connectivity (ODBC). ODBC must already be installed in order to make this selection.

Specifies that only the user who registered the database will have access to it.

Specifies that all users on the system will have access to the database.

Specifies that an ODBC data source file will be created. If TCP/IP is your protocol then the file can be shared.

Optional: Type a more meaningful name for the data source.

Specify the path and file name for the data source file.

Specify the application for which you want to tune the ODBC settings.

Shows:

Selecting a database displays related information in Target database and Comment.

Opens a window in which you can add to the list of systems known to the client.

Removes the selected systems from the list. You will be requested to confirm your selections.

Retrieves the latest information for the selected systems.

Specifies that the connection to the database is direct.

Specifies that the connection to the database is through a DB2 Connect gateway.

Specifies that you want to maintain the DB2 directories locally.

Specifies that you want to maintain the DB2 directories globally at an LDAP server.

Type a user ID that is valid for the LDAP server.

Type the password for the User ID.

Specifies that the Transmission Control Protocol/Internet Protocol (TCP/IP)will be used to connect to the database. If DB2 Connect is installed then The database physically resides on a host or OS/400 system check box is activated.

Specifies that Advanced Program-to-Program Communications (APPC) will be used to connect to the database. If DB2 Connect is installed then The database physically resides on a host or OS/400 system check box is activated.

Specifies that Advanced Peer-to-Peer Networking (APPN) will be used to connect to the database.

Specifies that NetBIOS will be used to connect to the database.

Specifies that Named pipes will be used to connect to the database.

Specifies that you are defining a connection to a database on your own system.

Select if DB2 Connect is installed on your computer and you want to specify the type of connection that you will make to the host or OS/400 database. Only available if TCP/IP, APPC, or APPN is your communication protocol.

Specifies that the connection to the database is direct.

Specifies that the connection to the database is through a DB2 Connect gateway. If your machine is the gateway then select Connect directly to the server.

Type the host name, Internet Protocol (IP) address, or IP name where the target database resides. Issuing the TCP/IP hostname command on the server system retrieves the server's host name. Issuing a ping hostname command will return the IP address of the host.

Type the service name of the server database manager instance. The Configuration Assistant expects that this name exists as a service name entry in the local TCP/IP services file. If an entry does not exist, no error is returned, but performing a test connection will fail. Specifying a Service name and a Port number will create an entry in the local TCP/IP services file.

Type the port number associated with the DB2 server instance that contains the target database. If you specified a Service name and that name exists in your local TCP/IP services file, you can click Retrieve to get the port number. You can type a port number without specifying a Service name.

Displays the port number associated with the Service name.

Type the symbolic destination name of the remote partner node. The name 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.

Specify the name of the remote partner node. You can click Configure to view or change the settings. Selecting <New> and Configure opens the Configure APPC Stack Wizard in which you can define a new symbolic destination name.

Displays the settings for the Connection symbolic destination name specified. If <New> was specified, then clicking Configure opens the Configure APPC Stack wizard in which you can define a new symbolic destination name.

Type the ID of the SNA network where the remote logical unit (LU) resides.

Type the logical unit (LU) name of the remote node.

Type the alias for the SNA local logical unit (LU) used for the connection.

Type the APPC transaction program name of the database server.

Type the SNA transmission mode used for the connection.

Type the LAN adapter address of the DB2 server.

Type the name of the partner logical unit (LU) that can be used when changing the password for a host database server.

Type the name of the remote workstation where the database resides. This is the workstation name found in the database manager configuration file on the server.

Type the client's workstation name. This is the workstation name found in the client instance database manager configuration file. If the name is available, this field will be automatically loaded.

Specify the adapter number used for outgoing connections. The default value is zero.

Type the computer name of the node where the target database resides.

Type the server instance name where the target database resides.

Specifies that the target database is in a different instance than the client.

Specify the instance where the target database resides.

Select the target database from the list.

Specifies that the target database and the client are in the same instance.

Specify the drive where the target database resides, or if UNIX the path.

Select the target database from the list.

Type an identifier for the target database.

Optional: Type a 1- to 8-character local nickname that can be used by applications running on your workstation to identify the database.

Optional: Type a comment that can be used in conjunction with the Database Alias to identify the database.

Type the name of the instance where the target database is located. This is the name identified by the DB2INSTANCE registry variable for the instance. You can issue the db2set DB2INSTANCE command in the server instance to retrieve its value.

Optional: Type a comment that can be used to identify the server and instance.

Specify the operating system where the target database is located.

Specify the computer, server system, or workstation where the target database is located. The initial value is the name you specified on the Specify the node options page.

Starts the search for the remote database that will be added. If a System name is specified, information is retrieved and the page is populated. If no System name is specified, a window opens from which you can select the appropriate TCP/IP system.

Specify the communications protocol that you will use to connect to the database. The initial value is the protocol that you specified on the Select a communications protocol page.

Type the host name, Internet Protocol (IP) address, or IP name where the target database resides. The initial value is the name that you specified on the Specify TCP/IP communication parameters page.

Retrieves the IP information if a host name is specified in the Host name field.

Select if authentication occurs through a firewall.

Type the symbolic destination name of the remote partner node. The initial value is the name that you specified on the Specify APPC communication parameters page.

Specify the symbolic destination name of the remote partner node. The initial value is the name that you specified on the Specify APPC communication parameters page. You can click Configure to view or change the settings. Selecting <New> and Configure opens the Configure APPC Stack wizard in which you can define a new symbolic destination name.

Displays the settings for the Connection symbolic destination name specified. If <New> was specified, then clicking Configure opens the Configure APPC Stack wizard in which you can define a new symbolic destination name.

Specify the authentication type defined in the database directory on the DB2 Connect workstation. This identifies where validation is performed.

Type the name of the remote workstation where the database resides. This is the workstation name found in the database manager configuration file on the server. The initial value is the name that you specified on the Specify NetBIOS communication parameters page.

Type the client workstation name. This is the workstation name found in the client instance database manager configuration file. The initial value is the name that you specified on the Specify NetBIOS communication parameters page.

Specify the adapter number used for outgoing connections. The initial value is the number that you specified on the Specify NetBIOS communication parameters page.

Type the computer name of the node where the target database resides. The initial value is the name that you specified on the Specify Named Pipes communication parameters page.

Type the server instance name where the target database resides. The initial value is the name that you specified on the Specify Named Pipes communication parameters page.

Type the name of the instance where the target database is located. This is the name identified by the DB2INSTANCE registry variable for the instance. You can issue the db2set DB2INSTANCE command in the server instance to retrieve its value.

Specify the operating system where the target database is located.

Optional: Type a comment that can be used to identify the server and instance.

Specifies that authentication is governed by the server instance's authentication configuration parameter.

Specifies that authentication occurs where the application is invoked using operating system security.

Specifies that authentication occurs on the server using its operating system security.

Select if the server accepts encrypted SERVER authentication schemes.

Specifies that authentication occurs on the host or OS/400 database server.

Specifies that the user is authenticated using DCE Security Services.

Type the name defined in the DCE Registry. Each DB2 user wishing to use a DCE-authenticated server must have a DCE principal and account defined in the DCE Registry with the client flag enabled. This principal must also have an entry in its Extended Registry Attributes (ERA) section.

Specifies that both the DB2 client and server are on operating systems that support the Kerberos security protocol.

Type the name used for Kerberos authentication.

Select if authentication occurs through a firewall.

Specify the authentication type defined in the database directory on the DB2 Connect workstation. This identifies where validation is performed.

Select to create an entry in the Database Connection Services (DCS) directory.

Type the value specified by a third party product. Some products may require that you override certain functions of DB2 Connect when connecting to host or OS/400 database servers. If you have not been directed to enter a value, or if you are unsure, leave this field blank.

Optional: Type a comment that can be used to identify the database.

Select to override the default SQLCODE mapping.

Type a mapping file name or click [...] to search for a mapping file.

Select to disconnect applications from the host or OS/400 database when an SQL300xx code is returned.

Select to have DB2 Connect perform the interrupt and disconnect.

Select to enable DB2 Connect SYSPLEX support for the DB2 for OS/390 database. If the target database is configured for data sharing, then each node of the SYSPLEX becomes equivalent. This allows DB2 Connect to balance connections across nodes and to provide fault tolerance if a node fails.

Select to enable the use of a bidirectional, coded character set.

Type the bidirectional, coded-character-set identifier (CCSID) number that you want to use. For bidirectional languages, a number of special character sets have been defined by IBM and are supported by DB2 Connect. If the bidirectional attributes of the database server are different from those of the client, you can use these special CCSID to manage the difference.

Select to activate date format support using date masks.

Type a date mask. For a date mask to be valid:

For example "YYyyMMdd" - Y, M, and D are not case-sensitive.

Select to perform password maintenance through the Configuration Assistant.

Specify the symbolic destination name that was specified in the CPI Communications Side Information Table. You should get this value from the person who installed or configured Systems Network Architecture (SNA). You must Configure new symbolic destination names.

Opens a window in which you specify the Logical Unit (LU) that will be used for password maintenance.