User's Guide

Collecting Information

Appendix A. "Directory Customization Worksheet" shows the information that you need to collect. You may find it convenient to make a copy of the worksheet and write in the values for your system.

Node Directory

You can specify the following information in the node directory:

Node name

A nickname for the DRDA server system on which the remote database resides. This name is user-defined. Write the same node name in both the Node Directory Parameters table and the System Database Directory Parameters table.

Format: 1-8 single-byte alphanumeric characters, including the number sign (#), at sign (@), dollar sign ($), and underscore (_). It cannot begin with an underscore or a number.

Protocol

Can be APPC or TCP/IP.

Symbolic destination name

When defining an APPC node, use the symbolic destination name that was specified in the CPI Communications Side Information Table (for example, the name of the CPI-C Symbolic Destination Properties when using Microsoft SNA Server). You should get this value from the person who either installed and/or configured SNA. The symbolic destination name is case sensitive (you may encounter an SQL1338 return code).

Security type

The type of security checking that will be done. For APPC nodes, the valid options are SAME and PROGRAM. For TCP/IP nodes, SECURITY SOCKS is an option which specifies that the node will be SOCKS-enabled, in which case the SOCKS_NS and SOCKS_SERVER environment variables are mandatory and must be set to enable SOCKS. For more information, see Chapter 6. "Security", and refer to the Command Reference.

TCP/IP remote hostname

When defining a TCP/IP node, either the remote TCP/IP hostname, or the remote TCP/IP address. If a hostname is specified, then it must be resolved at the DB2 Connect workstation, either through Domain Name Server (DNS) lookup, or by an entry in the local TCP/IP hosts file.

TCP/IP service name

When defining a TCP/IP node, either the remote TCP/IP service name or port number. This must be defined to TCP/IP at the remote host. Port number 446 has been registered as the default port number for DRDA.

Note:

A second port used for two-phase commit resynchronization operations over TCP/IP connections is assigned by the server. For example, the DB2 for OS/390 bootstrap dataset assigns the port number to be used for resynchronization for inbound connections to DB2 for OS/390 only. No service name need be defined for this.

DCS Directory

You can specify the following information in the DCS directory:

Database name

A user-defined nickname for the DRDA server database. Use the same database name in both the DCS Directory Parameters table and the System Database Directory Parameters table.

Format: 1-8 single-byte alphanumeric characters, including the number sign (#), at sign (@), dollar sign ($), and underscore (_). It cannot begin with an underscore or a number.

Target database name

The database on the DRDA server system, as follows:

MVS or OS/390: The LOCATION value
VSE or VM: The database name (DBNAME)
OS/400: The relational database name (RDBNAME)
Other: For OS/2 and UNIX-based systems, the database alias.

The default is the value that you specify for Database name.

Application requester

The name of the application requester that forwards SQL requests to DRDA application servers. The application requester handles requests on behalf of an application program. The default is the DB2 Connect application requester.

Parameter string

If you want to change the defaults, specify any or all the following parameters in the following order:

map-file: The name of an SQLCODE mapping file that overrides the default SQLCODE mapping. To turn off SQLCODE mapping, specify NOMAP.

For more information, see Chapter 8. "SQLCODE Mapping".

,D

The application will disconnect from the DRDA server database when this parameter (a comma followed by D) is used, and one of the following SQLCODES is returned:

SQL30053N
SQL30060N
SQL30070N
SQL30071N

SQL30072N
SQL30073N
SQL30074N
SQL30090N

When the disconnect parameter ,D is not specified, a disconnect will be performed only when the following SQLCODEs are returned:

SQL30020N SQL30021N

SQL30041N SQL30061N

SQL30081N

For explanations of these codes, see the Message Reference.
Note: If DB2 Connect disconnects due to an error, a rollback will be done automatically.

,,INTERRUPT_ENABLED

If INTERRUPT_ENABLED is configured in the DCS directory at the DB2 Connect workstation, and a client application issues an interrupt while connected to the DRDA server, DB2 Connect will perform the interrupt by dropping the connection and rolling back the unit of work. This interrupt behavior is supported on AIX, OS/2, and Windows NT.

The application will receive sqlcode (-30081) indicating that the connection to the server has been terminated. The application must then establish a new connection with the DRDA server, in order to process additional database requests. Note that on platforms other than AIX V4.1 with SNA Server V3.1, OS/2, and Windows NT, DB2 Connect does not support the option of automatically disconnecting when an application using it receives an interrupt request.
Note: This support works for TCP/IP connections on any platforms. The client may kill the socket, but - depending on the server implementation - there may or may not be an outstanding receive. DB2 for OS/390 utilizes asynchronous socket calls and therefore is able to detect the loss of the connection and roll back any long-running SQL statements that are in progress.

For example, you could specify any of the following:

On AIX:
 
   NOMAP
   /u/username/sqllib/map/dcs1new.map,D
   ,D
   ,,INTERRUPT_ENABLED
 
On OS/2:
 
   NOMAP
   d:\sqllib\map\dcs1new.map,D
   ,,INTERRUPT_ENABLED

or accept the defaults by not specifying a parameter string.

System Database Directory

You can specify the following information in the system database directory:

Database name

The same value that you wrote in the DCS Directory Parameters table.

Database alias

An alias for the DRDA server database. This name will be used by any application program that accesses the database. By default, the value that you specify for Database name is used.

Format: 1-8 single-byte alphanumeric characters, including the number sign (#), at sign (@), dollar sign ($), and underscore (_). It cannot begin with an underscore or a number.

Node name

The same value that you wrote in the Node Directory Parameters table.

Authentication

Specifies where the validation of the user's name and password will be done. The valid options are: SERVER, CLIENT, DCE, and DCS. For more information, see Chapter 6. "Security".

Defining Multiple Entries for the Same Database

For each database, you must define at least one entry in each of the three directories (node directory, DCS directory, and system database directory). In some cases, you might want to define more than one entry for the database.

For example, you might want to turn off SQLCODE mapping for applications that were ported from the DRDA server but accept the default mapping for applications that were developed for the client/server environment. You would do this as follows:

Define one entry in the node directory.
Define two entries in the DCS directory, with different database names. For one entry, specify NOMAP in the parameter string.
Define two entries in the system database directory, with different database aliases and the two database names that you specified in the DCS directory.

Both aliases access the same database, one with SQLCODE mapping and the other without SQLCODE mapping.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]