Populating the communications database
If you plan to use DB2® only as a server, you do not need to populate the CDB; default values are used. However, if you intend for DB2 to act as a requestor, you need to insert one row for each remote system into SYSIBM.LOCATIONS and SYSIBM.LUNAMES.
About this task
For example, Spiffy's USIBMSTODB21 subsystem works as a server for many Windows requesters. It is not necessary for Spiffy to register all those requesters in the DB2 CDB.
You do not need to populate table SYSIBM.LULIST unlessDB2 is acting as a requester of data that resides in a data sharing group.
After you populate these tables, you can write queries that access data at a remote system.
- VTAM-relevant columns of the SYSIBM.LOCATIONS table
When you
issue an SQL CONNECT statement, the LOCATION column of the SYSIBM.LOCATIONS
table correlates the location name (or DRDA RDBNAM)
with the VTAM LU name. If necessary,
the location name is also correlated with the transaction program
names (TPNs).
- VTAM-relevant columns of the SYSIBM.LUNAMES table
The LUNAMES table defines the security and mode requirements for conversations with other systems. Decisions about how to populate this table depend on how you intend to use DB2. - VTAM-relevant columns of the SYSIBM.USERNAMES table
SYSIBM.USERNAMES contains information that is needed for outbound and inbound ID translation and also for "come from" checking.
Parent topic: Connecting systems with VTAM
Previous topic: Defining the DB2 subsystem to VTAM
Next topic: Starting VTAM to use DB2
Related concepts:
Related tasks: