Populating the communications database for use with TCP/IP
If you plan to use DB2® only as a server, you do not need to populate the CDB.
About this task
For example, Spiffy's USIBMSTODB21 subsystem works as a server for many requesters. It is not necessary for Spiffy to register those requesters in the DB2 CDB.
However, if you intend to request data, you need to enter port numbers or service names in field PORT of table SYSIBM.LOCATIONS, and IP addresses or domain names in field IPADDR of table SYSIBM.IPNAMES. The LINKNAME in table SYSIBM.LOCATIONS is used to search tables SYSIBM.IPNAMES and SYSIBM.LUNAMES.
Updates to the following tables take place whenever a
new remote connection is requested, without any need to stop and restart
DDF:- SYSIBM.LOCATIONS
- SYSIBM.IPNAMES
- SYSIBM.IPLIST
If you use RACF® PassTickets, the LINKNAME must match the following values at the remote site:
- LUNAME
If the remote site is a DB2 subsystem that is defined with only an LUNAME value and no GENERIC LU name value or IPNAME value.
- GENERIC
If the remote site is a DB2 subsystem that is defined with a GENERIC LU name value in addition to an LUNAME value, but no IPNAME value.
- IPNAME
If the remote site is a DB2 subsystem that is defined with an IPNAME value, which triggers the DDF on the remote DB2 subsystem to activate TCP/IP communications support only.
After you populate these tables, you can write queries that access data at a remote system.
