| Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Add Relational Database Directory Entry (ADDRDBDIRE) command allows you to add an entry to the relational database directory. Relational database (RDB) entries can represent local databases or remote databases. The RDB associated with an entry can also be classified as a system database or a user database.
There is only one system database per system. It is defined as the system auxiliary storage pool (ASP number 1) and configured basic user ASPs (ASP numbers 2-32). A system can be configured to have one or more user databases. A user database is defined to be an ASP group that is configured and available. Such a database is joined to the system database in such a way that all of the objects on the system database are also accessible through it.
Note: As used in this context, 'system' can refer a logical partition of a System i machine configured with multiple partitions.
Local databases include the system database and any available user databases on this system. Remote databases normally reside on another system, but an unavailable ASP group configured on this system is also considered to be temporarily remote, because it might have been switched to another node within a cluster of systems.
Restrictions:
| Top |
| Keyword | Description | Choices | Notes |
|---|---|---|---|
| RDB | Entry | Element list | Required, Key, Positional 1 |
| Element 1: Relational database | Character value | ||
| Element 2: Relational database alias | Character value, *NONE | ||
| RMTLOCNAME | Remote location | Single values: *ARDPGM, *LOOPBACK Other values: Element list |
Required, Positional 2 |
| Element 1: Name or address | Character value, *LOCAL | ||
| Element 2: Type | *SNA, *IP | ||
| PORT | Port number or service program | Character value, *DRDA | Optional |
| RMTAUTMTH | Remote authentication method | Element list | Optional |
| Element 1: Preferred method | *USRENCPWD, *USRID, *USRIDPWD, *ENCUSRPWD, *KERBEROS, *ENCRYPTED | ||
| Element 2: Allow lower authentication | *ALWLOWER, *NOALWLOWER | ||
| ENCALG | Encryption algorithm | *DES, *AES | Optional |
| SECCNN | Secure connection | *NONE, *SSL | Optional |
| DEV | Device | Element list | Optional |
| Element 1: APPC device description | Name, *LOC | ||
| LCLLOCNAME | Local location | Communications name, *LOC, *NETATR | Optional |
| RMTNETID | Remote network identifier | Communications name, *LOC, *NETATR, *NONE | Optional |
| MODE | Mode | Communications name, *NETATR | Optional |
| TNSPGM | Transaction program | Character value, *DRDA | Optional |
| ARDPGM | Application requester driver | Single values: *DRDA Other values: Element list |
Optional |
| Element 1: Program | Qualified object name | ||
| Qualifier 1: Program | Name | ||
| Qualifier 2: Library | Name, *LIBL, *CURLIB | ||
| TEXT | Text | Character value, *BLANK | Optional |
| Top |
Specifies the relational database name information.
This is a required parameter.
Note: Valid relational database names and aliases can contain any of the following: A-Z, 0-9, @, #, $ and _.
Element 1: Relational database
Element 2: Relational database alias
| Top |
Specifies the remote location name of the system on which the relational database (RDB) is located.
This is a required parameter.
Single values
Note: If *ARDPGM is specified, the PORT, DEV, LCLLOCNAME, RMTNETID, MODE, and TNSPGM parameters are ignored.
Note: If *LOOPBACK is specified, the DEV, LCLLOCNAME, RMTNETID, MODE, TNSPGM and ARDPGM parameters are ignored, and the value of the second element is forced to *IP.
Element 1: Name or address
Note: If *LOCAL is specified, the DEV, LCLLOCNAME, RMTNETID, MODE, TNSPGM and ARDPGM parameters are ignored, and the value of the second element is forced to *IP. A relational database alias name is not valid when specified with a *LOCAL remote location name.
If *IP is specified for the second element, the DRDA server at the remote location must support the use of TCP/IP, and the DEV, LCLLOCNAME, RMTNETID, MODE, and TNSPGM parameters will be ignored.
If *SNA is specified for the second element, the DRDA server must support SNA connectivity. More information about SNA remote location names can be found in the APPC Programming book, SC41-5443 and the APPN information in the Networking category in the IBM i Information Center at http://www.ibm.com/systems/i/infocenter/.
Element 2: Type
| Top |
Specifies the TCP/IP port that is used at the remote location to communicate with the system on which the RDB is located. This parameter will be ignored if *IP is not specified in the RMTLOCNAME parameter.
| Top |
Specifies the preferred remote authentication method on a DDM/DRDA TCP/IP connection request. The actual method used depends on the outcome of the negotiation process between client and server, which depends on the cryptographic support available and the server security configuration. The CHGDDMTCPA (Change DDM TCP/IP Attributes) command can be used to configure DDM/DRDA TCP/IP security on i5/OS systems. This parameter will be ignored if *IP is not specified in the Remote location (RMTLOCNAME parameter).
Element 1: Preferred method
Specifies the initial authentication method proposed to the server. Based on the authentication methods supported by the server and the value specified for the Allow lower authentication element of this parameter, an authentication method is negotiated that is acceptable to both the client and server.
Note: The following value is only supported for compatibility with the releases earlier than Version 5 Release 5 Modification 0 of the operating system.
Element 2: Allow lower authentication
Specifies whether an authentication method lower than what was specified for the Preferred method element of this parameter will be accepted during negotiation with the server. If the server is configured to require a higher authentication method than the value specified for the Preferred method element of this parameter and the Application Requester system can support a higher authentication method, the negotiated authentication method can always be higher than the Preferred method. From highest to lowest strength, the authentication methods are:
| Top |
Specifies the encryption algorithm to be initially used on a DDM/DRDA TCP/IP connection request when encrypting the userid and password. The actual encryption algorithm used depends on the outcome of the negotiation process between client and server, which depends on the cryptographic support available and the server security configuration. The CHGDDMTCPA (Change DDM TCP/IP Attributes) command can be used to configure DDM/DRDA TCP/IP security on i5/OS systems. This parameter will be ignored if *IP is not specified in the Remote location (RMTLOCNAME parameter). The possible values are:
From highest to lowest strength, the encryption algorithms are:
| Top |
Indicates whether Secure Sockets Layer (SSL) is to be used on a DDM/DRDA TCP/IP connection request. The possible values are:
| Top |
Specifies the advanced program-to-program communications (APPC) device description on this system that is used with this relational database (RDB) entry.
More information on device names is in the APPC Programming book, SC41-5443.
| Top |
Specifies the local location name by which this system is identified to the system on which the RDB is located. The local location name cannot be the same as the remote location name.
| Top |
Specifies the remote network identifier of the system on which the RDB is located. If this parameter is specified, the RMTLOCNAME parameter must be consistent with this RMTNETID parameter. If the RMTLOCNAME parameter specified a network ID, this parameter must agree (otherwise, an error message will be issued). If the RMTLOCNAME parameter does not specify any network ID, there is no possibility of conflict with this parameter.
More information on remote network identifiers is in the APPC Programming book, SC41-5443.
| Top |
Specifies the mode name to use with the remote location name to communicate with the system on which the RDB is located.
| Top |
Specifies the name of the transaction program to use with the RDB entry.
| Top |
Specifies the application requester driver that is the program to be called to process SQL requests directed to the RDB. The program must exist in a library that is located in the system database (system ASP or a configured basic user ASP) on this system, and must be of the object type *PGM.
Single values
Qualifier 1: Program
Qualifier 2: Library
| Top |
Specifies the text that briefly describes the object.
| Top |
Example 1: Adding an Entry
ADDRDBDIRE RDB(MYRDB)
RMTLOCNAME(*LOCAL)
This command adds an entry to the relational database directory. The entry identifies the local relational database. In an SQL program, this relational database name is used when referring to the local relational database.
Example 2: Adding an Entry
ADDRDBDIRE RDB(YOURRDB)
RMTLOCNAME(NEWYORK)
This command adds an entry to the relational database directory. The entry identifies a remote location, NEW YORK.
Example 3: Adding an Entry for an Application Requester Driver Program
ADDRDBDIRE RDB(YOURRDB)
RMTLOCNAME(*ARDPGM)
ARDPGM(MYLIB/MYPGM)
This command adds an entry to the relational database directory. The entry indicates that access to relational database YOURRDB will be done by an application requester driver program named MYPGM in the library MYLIB.
Example 4: Adding an Entry for TCP/IP usage
ADDRDBDIRE RDB(TCPRDB)
RMTLOCNAME(ROCHESTER.XYZ.COM *IP)
PORT(*DRDA)
This command adds an entry to the relational database directory. The entry specifies that the remote RDB associated with the RDB name of TCPRDB uses TCP/IP and is on the host with the domain name of ROCHESTER.XYZ.COM, and listens on the standard DRDA port of 446 (*DRDA is the default port so the PORT parameter is unnecessary in this case).
Example 5: Adding an Entry for TCP/IP using Dotted Decimal IP Version 4 Address and a Numeric Port Number
ADDRDBDIRE RDB(DB2DSYS)
RMTLOCNAME('9.5.36.17' *IP)
PORT(5021)
This command adds an entry to the relational database directory. The entry specifies that the remote RDB associated with the RDB name of DB2DSYS uses TCP/IP and is on the host with an IP address of 9.5.36.17, and listens on port 5021. A System/390 MVS installation, for example, can have multiple DB2 subsystems, and TCP/IP can support only one server at each port number, so port numbers other than 446 are sometimes required.
Example 6: Adding an Entry for TCP/IP using Colon Hexadecimal IP Version 6 Address and a Numeric Port Number
ADDRDBDIRE RDB(DB2DSYS)
RMTLOCNAME('2001:DB8:0:B33D:8785:0:1734:F51C' *IP)
PORT(32)
This command adds an entry to the relational database directory. The entry specifies that the remote RDB associated with the RDB name of DB2DSYS uses TCP/IP and is on the host with an IP address of 2001:DB8:0:B33D:8785:0:1734:F51C, and listens on port 32. A System/390 MVS installation, for example, can have multiple DB2 subsystems, and TCP/IP can support only one server at each port number, so port numbers other than 446 are sometimes required.
Example 7: Adding an Entry for TCP/IP using a Service Name for the Port Identification
ADDRDBDIRE RDB(DB2ESYS)
RMTLOCNAME(ROCHESTER.XYZ.COM *IP)
PORT(DB2ESYS_PORT)
This command uses a service name to specify the port number when adding a new entry. The operating system will attempt to resolve the name DB2ESYS_PORT to a port number by use of the TCP/IP Service Table. In order for the name to be properly resolved, an entry for DB2ESYS_PORT must exist in the TCP/IP Service Table. The WRKSRVTBLE or CFGTCP command can be used to update the service table.
| Top |
| Top |