The SYSIBM.IPNAMES table defines the remote DRDA servers DB2® can
access using TCP/IP.
Rows in this table can be inserted, updated, and deleted.
| Column name |
Data type |
Description |
Use |
|---|
| LINKNAME |
VARCHAR(24)
NOT NULL
|
The value specified in this column must match the
value specified in the LINKNAME column of the associated row in SYSIBM.LOCATIONS. |
G |
| SECURITY_OUT |
CHAR(1)
NOT NULL
WITH DEFAULT 'A'
|
This column defines the DRDA security option that is used when local DB2 SQL applications connect to
any remote server associated with this TCP/IP host: - A
- The option is "already verified". Outbound connection requests
contain an authorization ID and no password. The authorization ID
used for an outbound request is either the DB2 user's authorization ID or a translated ID,
depending upon the value of the USERNAMES column.
The authorization
ID is not encrypted when it is sent to the partner. For encryption,
refer to 'D'.
- D
- The option is "userid and security-sensitive data encryption".
Outbound connection requests contain an authorization ID and no password.
The authorization ID used for an outbound request is either the DB2 user's authorization ID or a
translated ID, depending upon the value of the USERNAMES column.
This
option indicates that the userid and security-sensitive data are to
be encrypted. For non-encryption, refer to 'A'.
- E
- The option is "userid, password, and security-sensitive data
encryption". Outbound connection requests contain an authorization
ID and a password. The password is obtained from the SYSIBM.USERNAMES
table. The USERNAMES column must specify 'O'.
This option indicates
that the userid, password, and security-sensitive data are to be encrypted.
For non-security-sensitive data encryption, refer to 'P'.
If the applications connect to any remote server as trusted,
the USERNAMES column must specify 'O' or 'S'.
|
G |
| SECURITY_OUT (continued) |
|
- P
- The option is "password". Outbound connection requests contain
an authorization ID and a password. The password is obtained from
the SYSIBM.USERNAMES table. The USERNAMES column must specify 'O'.
This
option indicates that the userid and the password are to be encrypted
if cryptographic services are available at the requester and if the
server supports encryption. Otherwise, the userid and the password
are sent to the partner in clear text. For security-sensitive data
encryption, see 'E'.
If the applications connect
to any remote server as trusted, the USERNAMES column must specify
'O' or 'S'.
- R
- The option is "RACF® PassTicket".
Outbound connection requests contain a userid and a RACF PassTicket. The value specified in
the LINKNAME column is used as the RACF PassTicket
application name for the remote server.
The authorization
ID used for an outbound request is either the DB2 user's authorization ID or a translated ID,
depending upon the value of the USERNAMES column.
The authorization
ID is not encrypted when it is sent to the partner.
|
|
| USERNAMES |
CHAR(1)
NOT NULL WITH
DEFAULT
|
This column controls outbound authorization ID
translation. Outbound translation is performed when an authorization
ID is sent by DB2 to a remote
server. - O
- An outbound ID is subject to translation. Rows in the SYSIBM.USERNAMES
table are used to perform ID translation.
No translation or "come
from" checking is performed on inbound IDs.
- S
- Row in the SYSIBM.USERNAMES table is used to obtain the system
AUTHID used to establish a trusted connection.
- blank
- No translation occurs.
|
G |
| IBMREQD |
CHAR(1)
NOT NULL WITH
DEFAULT 'N'
|
A value of Y indicates that the row came from the
basic machine-readable material (MRM) tape. For all other values,
see Release
dependency indicators. The value in this field is not a reliable indicator of release dependencies.
|
G |
| IPADDR |
VARCHAR(254)
NOT NULL WITH
DEFAULT
|
This column contains an IPv4 or
IPv6 address, or domain name of a remote TCP/IP host. The IPADDR column
must be specified as follows:
- An IPv4 address must be left justified and is represented as a
dotted decimal address. For example, '123.456.78.91' would be interpreted
as an IPv4 address.
- An IPv6 address must be left justified and is represented as a
colon hexadecimal address. An example of an IPv6 address is '2001:0DB8:0000:0000:0008:0800:200C:417A',
which can also be expressed in compressed form as '2001:DB8::8:800:200C:417A'.
- A domain name is converted to an IP address by the domain name
server where a resulting IPv4 or IPv6 address is determined. An example
of a domain name is 'stlmvs1.svl.ibm.com'.
|
G |