You can specify the following information in the node directory:
- Node name
- A nickname for the IBM mainframe
database 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
- Must be TCP/IP.
- Security type
- The type of security checking that will be done. 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.
- TCP/IP remote hostname or IP address
- 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.
For DB2® for z/OS® remote
hosts, the hostname appears in the DSNL004I message (DOMAIN=hostname)
when the Distributed Data Facility (DDF) is started. The -DISplay
DDF command could also be used.
If accessing
a z/OS data sharing group,
the domain name should map to the DB2 group
dynamic VIPA address. This address routes to the least loaded DB2 member. To access a specific
member use the specific DB2 member
dynamic VIPA address and turn off sysplex routing. Each member DSNL004I
message displays the member specific domain name.
- TCP/IP service name or port number
- 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®.
For DB2 for z/OS remote
hosts, the port number is defined in the Boot Strap Data Set (BSDS)
as PORT and is also provided in the DSNL004I message (TCPPORT=portnumber)
when the Distributed Data Facility (DDF) is started. The -DISplay
DDF command could also be used.
If accessing
a z/OS data sharing group,
the domain name should map to the DB2 group
dynamic VIPA address. This address routes to the least loaded DB2 member. To access a specific
member use the specific DB2 member
dynamic VIPA address and turn off sysplex routing. Each member DSNL004I
message displays the member specific domain name.
Note: A second
port used for two-phase commit resynchronization operations over TCP/IP
connections can be assigned by the server. For example, the DB2 for z/OS bootstrap
data set assigns a port number (RESPORT) to be used for resynchronization
for inbound connections to DB2 for z/OS only.
No service name need be defined for this.
DB2 Version 9.7 for Linux, UNIX, and Windows