If you plan to deploy DB2 Data Links Manager in a Journaled File System (JFS) environment, you should also take the following information into consideration:
When you select to create the DLMADMIN username, the db2setup utility will create this user with the username dlfm and password ibmdb2. You can accept these default values, specify an existing username, or create a different username by changing the default values. For security reasons, we recommend that you specify your own username and password because the default values are used in every DB2 Data Links installation and therefore are well known. The DLMADMIN username will also be the name of the Data Links Manager instance.
If you want to specify your own existing username, the account you specify:
To create a username for use as the DB2 Data Links Manager Administrator (DLMADMIN):
mkgroup dlfmgrp mkuser pgrp='dlfmgrp' groups='dlfmgrp' home='/home/dlfm' dlfm
The DB2 Data Links Manager Administrator (DLMADMIN) should never own files or directories on a file system that is under the control of a Data Links Filesystem Filter. The DLMADMIN should only be used to administer the Data Links File Manager.
If you create a different username by changing the default values, you must ensure that the username you specify is eight characters or less.
When connecting to the DB2 Data Links File Manager, the DB2 UDB server sends the following information to the DLFM:
The DLFM then verifies this information to decide if a connection from this particular DB2 server should be allowed. The subroutine that obtains hostname information on the DB2 server, gethostbyname, looks for /etc/resolv.conf. If this file exists, the subroutine queries the domain name server. If the request to the DNS times out, the gethostbyname routine checks the local /etc/hosts file. To connect successfully to the DLFM, the name registered on the DLFM must be the one which is obtained by the gethostbyname routine on the DB2 UDB server.
To resolve the hostnames of your DB2 Data Links and DB2 UDB servers, enter the hostname command on each system. For example, this command might return dlmserver on your Data Links server.
Now enter the host dlmserver command, where dlmserver is your hostname. This command should return output similar to the following:
dlmserver.services.com is 9.11.302.341, Aliases: dlmserverdlmserver.services.com is your fully qualified hostname name.
Repeat these steps on each DB2 Data Links and DB2 UDB server.