Remote location

Displays the properties of the remote system that you have selected.

Name or Address

Specifies the remote location name of the system on which the relational database is located.

The possible values are:

Loopback which indicates that the relational database is accessed using the internet protocol loopback or local host address. The use of Loopback allows a distributed relational database architecture (DRDA) connection to the local system.

Note: If Loopback is specified, the device, local location name, remote network identifier, mode, transaction program, and application requester driver parameters are ignored and the communications type is forced to TCP/IP.

  • A user-specified remote location name which can take one of several forms:
    • System Network Architecture (SNA) remote location name (LU name). Specify a maximum of eight characters for the remote location name. If this form is used, the communications type must be SNA.
    • SNA remote network identifier and remote location name separated by a period. Specify a maximum of eight characters for the remote location name, and a maximum of eight characters for the remote network identifier. If this form of the parameter is used, the communications type must be SNA, and any value specified for the remote network identifier parameter must agree.
    • TCP/IP address in dotted decimal form. Specify an internet protocol address in the form nnn.nnn.nnn.nnn where each nnn is a number in the range 0 through 255. If this form is used, the communications type of this parameter must be specified as TCP/IP.
    • TCP/IP host domain name. Specify an internet host domain name of up to 254 characters in length. If this form is used, the communications type must be specified as TCP/IP.

  • Application requester driver which indicates that the relational database is accessed using the application requester driver program specified. In this case, a remote location name is not used to locate the relational database.

    Note: If application requester driver is specified, the port, device, local location name, remote network identifier, mode, and transaction program parameters are ignored.


Communications type
Specifies the communications protocol used to access the database. The possible types are SNA (System Network Architecture) and TCP/IP.

Note: If TCP/IP is specified for the communications type, the DRDA applications server at the remote location must support the use of TCP/IP, and the device, local location name, remote network identifier, mode, and transaction program parameters will be ignored. If TCP/IP is not specified, the application server must support SNA connectivity.

Port number or service program
Specifies the TCP/IP port that is used at the remote location to communicate with the system on which the relational database is located. This parameter is ignored if TCP/IP is not specified as the communications type.

The possible values are:

  • DRDA which indicates that the port 446 is used.
  • User-specified values which are port numbers ranging from 1 to 65535, or a service name that can be up to 14 characters.

Authentication method

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 system security configuration. The CHGDDMTCPA command can be used to configure DDM/DRDA TCP/IP security on the System i product. This parameter is ignored if TCP/IP is not specified in the remote location name.

The preferred method specifies the initial authentication method proposed to the server. Based on the authentication methods supported by the system and whether the allow lower authentication option is selected, an authentication method is negotiated that is acceptable to both the application requester and the application server systems.

Possible values are:

  • Encrypted which indicates that the userid and associated encrypted password is sent on a distributed data management (DDM) connection request. Cryptographic support must be available on both systems for this authentication method to be used.
  • Userid only which indicates that only the userid is sent on a DDM connection request. This is the lowest authentication method.
  • Userid and password which indicates that the userid and associated password is sent on a DDM connection request. Passwords are not encrypted if this authentication method is used.
  • Kerberos which indicates that authentication occurs using Kerberos. With this method, the relational database name must map to a target principal name in the Enterprise Identity Mapping (EIM) environment. Kerberos needs to be configured on both systems for this authentication method to be used.

Note: The Kerberos authentication method does not apply to i5/OS Version 5 Release 1 or earlier versions.

Allow negotiation to lower authentication method
Specifies whether an authentication method lower than what was specified for the preferred method will be accepted during negotiation with the application server system. If the application server system is configured to require a higher authentication method than the value specified for the preferred method and the application requester system can support a higher authentication method, the negotiated authentication can always be higher than the preferred method. From highest to lowest, the authentication methods are:
  • Kerberos
  • Encrypted
  • User ID and password
  • User ID

Device description
Specifies the name of the advanced program-to-program communications (APPC) device description on this system that is used with this relational database.

The possible values are:

  • System-defined which indicates that when advanced program-to-program communications (APPC) is used the system determines which device description to use. Or, if advanced peer-to-peer networking (APPN) is used, the system ignores this parameter.
  • A user-specified value with a maximum of 10 characters for the name of a device description.

Local location name
Specifies the local location name by which this system is identified to the system on which the relational database is located. The local location name cannot be the same as the remote location name.

The possible values are:

  • System-defined which indicates that when advanced program-to-program communications (APPC) is used the system determines which local location name to use. Or, if advanced peer-to-peer networking (APPN) is used, the system uses the default local location defined in the network attributes.
  • Use network attributes which indicates that the local location name specified in the system network attributes is used. You can also specify a maximum of eight characters for the local location name.

Remote network ID
Specifies the remote network identifier of the system on which the relational database is located. If this parameter is specified, the remote location name parameter must be consistent with this remote network identifier parameter. If the remote location name parameter specified a network identifier, this parameter must agree (otherwise, an error message will be issued).

If the remote location name parameter does not specify any network identifier, there is no possibility of conflict with this parameter.

The possible values are:

  • System-defined which indicates that when advanced program-to-program communications (APPC) is used the system determines which remote network identifier to use. Or, if advanced peer-to-peer networking (APPN) is used, the system uses the local network identifier defined in this system's network attributes for the remote network identifier.
  • Use network attributes which indicates that the local network identifier specified in the system network attributes is used. You can also specify a maximum of eight characters for the remote network identifier.
  • None which indicates that there is no remote network identifier

Mode
Specifies the mode name to use with the remote location name to communicate with the system on which the relational database is located.

The possible values are:

  • Use network attribute which indicates that the mode in the network attributes is used.
  • Use blanks which indicates that a mode name of all blanks is used. You can also specify a maximum of eight characters for the mode name.

Transaction program
Specifies the name of the transaction program to use with the relational database.

The possible values are:

  • DRDA standard program which indicates that the distributed relational database architecture (DRDA) transaction program name, X'07F6C4C2', is used. DRDA is a method by which relational databases communicate with each other over a network.
  • A user-specified transaction program name in one of the following formats:
    • A four-byte hexadecimal name, which is entered by enclosing the eight hexadecimal digit in apostrophes with a prefix of X. For example, X'07F6C4C2' is a four-byte hexadecimal name.
    • An eight-byte character name

Program
Specifies the name of the application requester driver program.

Schema
Specifies the name of the schema in which the application requester driver program is located.