DB2 Data Links Manager Quick Beginnings

Manually installing DB2 Data Links Manager Using SMIT

We recommend that you use the db2setup utility to install DB2 Data Links Manager for AIX. If you prefer not to use this utility, you can manually install the DB2 Data Links Manager software bundle using AIX's System Management Interface Tool (SMIT).

Unless otherwise noted, these steps are the same for DB2 Data Links installations in Journaled File System (JFS) and DCE-DFS environments on AIX.

To install a DB2 Data Links Manager software bundle using SMIT:

Log in as a user with root authority.
Insert and mount the appropriate CD-ROM.
Enter the smit command.
Select Software Installation and Maintenance --> Install and Update Software --> Install Software Bundle (Easy Install).
Specify the input device or directory for the installation media, or click List to display all input devices or directories.
Select the CD-ROM drive you mounted, then press Enter.
Select the DB2V7DLNK bundle and press Enter. The Install Software Bundle window opens.
Review the bundle installation parameters. In particular, make sure that COMMIT software updates and AUTOMATICALLY install requisite software are set to yes. Click OK again to begin installation.
If you did not install the DB2 Media-Defined software bundle on this system, use the following procedure to install it:
1. In the Bundle to Install menu, select the Media-Defined option, then press Enter.
2. In the Install Bundle Contents menu, press Enter to continue with the installation. Messages may appear to indicate the status of the installation. Press Enter to continue.
3. Press F3 to return to the Install Bundle Contents menu.
4. Press F4 to re-display the list of software bundles. Select the bundle you want to install and press Enter to begin the installation process. DB2 will be installed in the /usr/lpp/db2_07_01/ directory.

SMIT post-installation tasks

After manually installing the Data Links Manager software bundle, you must perform several additional configuration tasks. If you used the db2setup utility to install your product all of these tasks, except step 3 (setting up a DFS disk archive directory), were performed for you.

Unless otherwise noted, these tasks apply to Data Links Manager installations in native JFS and DCE-DFS environments.
Note: In DCE-DFS environments, the following tasks assume you have already created a DCE identity for use by the Data Links File Manager. In the examples below, we will assume that the DLFM username you created is dlfmuser. For more information on creating and administering DCE identities, see Appendix C, DCE-DFS Common Tasks and References or refer to your Transarc DCE-DFS product documentation.

To complete your manual DB2 Data Links Manager installation:

As a user with root authority on the DLFM server, run the /usr/lpp/db2_07_01/instance/dlfmcrt command to create a DLFM instance.
DCE-DFS only: On the DLFM server and each DLFM client, set the DLFM_FS_ENVIRONMENT registry variable to DFS as follows:
```
   db2set DLFM_FS_ENVIRONMENT=DFS
```
DCE-DFS only in installations performed using db2setup or SMIT: On the DLFM server and each DLFM client, set up the disk archive directory.
Consider the following scenario:
- Your DCE cellname is dln1.almaden.ibm.com.
- You have two nodes in the cell: node1.almaden.ibm.com (known as node1), and node2.almaden.ibm.com (known as node2).
- There are two prefixes registered with the DFS File Manager:
  - /.../dln1.almaden.ibm.com/fs/prfx1. This prefix is native to node1. The prefix is prfx1. The fileset name is fileset1.
  - /.../dln1.almaden.ibm.com/fs/prfx2. This prefix is native to node2. The prefix is prfx2. The fileset name is fileset2.
The archive directory must be a DFS fileset. For example, you may use /.../dln1.almaden.ibm.com/fs/dlfm_backup/ as your archive directory.
In this scenario, you would set the DLFM_BACKUP_DIR_NAME registry variable on the DLFM server and each DLFM client as follows:
```
   db2set DLFM_BACKUP_DIR_NAME=/.../dln1.almaden.ibm.com/fs/dlfm_backup
```
For files that reside in prfx1, the archive will be made by the copy daemon running on node1 to the /.../dln1.almaden.ibm.com/fs/dlfm_backup/node1/_prfx1/ directory. For files in prfx2, the archive will be made to the /.../dln1.almaden.ibm.com/fs/dlfm_backup/node2/_prfx2/ directory.
The directories /.../dln1.almaden.ibm.com/fs/dlfm_backup/node* and /.../dln1.almaden.ibm.com/fs/dlfm_backup/node*/_prfx1/ will be created when you issue the dlfm start command, below.
DCE-DFS only: If you are installing a DLFM server or client, edit the /etc/services files at each node. Add two consecutive port numbers for the service name, srv_dlfm. For example, if the service name is datalsrv, you would add datalsrv and datalsrv_i to /etc/services.
Set the DLFM_PORT registry variable to a an unused port number by entering the following command:
```
   db2set DLFM_PORT=port_number
```
where port_number is any unused communications port number. We recommend you also add this entry to your /etc/services file so that no other services use this port.
DCE-DFS only: If you are installing a DLFM server, dce_login as the DLMADMIN user and run the dlfm server_conf srv_dlfm command, where srv_dlfm is the service name of the Data Links Manager server. This will automatically create the dlmnodes.cfg and dlfs.cfg files.
The dlmnodes.cfg file contains a header and entries for each node. The header contains the name of the file, version number, number of nodes, entry number of the Data Links Manager server node, and a checksum. The node entries each contain the node name, port number, and node type (either server or client).
The dlfs.cfg file contains configuration information about the DLMADMIN user and the DCE cell.
Run the dlfm setup command. DCE-DFS only: Run this command on the DLFM server only.
DCE-DFS only: If you are installing a DLFM client on a DCE-DFS node, dce_login as the DLMADMIN user and run the dlfm client_conf srv_dlfm node_alias remote_server command, where:
- srv_dlfm is the service name of the Data Links Manager client on this node.
- node_alias is the alias to be used for this node.
- remote_server is the name of the Data Links Manager server node in this DCE cell.
This will automatically add an entry for this node in the dlmnodes.cfg file on the server.
DCE-DFS only: If you are installing DLFM clients, edit each client's /etc/services file. Add two consecutive port numbers for the service name, srv_dlfm, you specified in the previous step. For example, if the service name is datalclt, you would add datalclt and datalclt_i to /etc/services.
DCE-DFS only: On the DLFM server, back up any files under /:/Datalinks.
DCE-DFS only: Register the data manager application (DMAPP) in the DFS pre-start script as follows:
1. Check if /opt/dcelocal/tcl/user_cmd.tcl exists. If it does not exist, create it.
2. Append the following line to /opt/dcelocal/user_cmd.tcl:
```
   set pre_start_dfs "/usr/bin/dlfsdmap_prestart.dfs"
```
3. Create a link from $HOME/sqllib/adm/dlfsdmap_prestart.dfs to /usr/bin/dlfsdmap_prestart.dfs.
Run the dlfm start command on each server. In DCE-DFS environments, run this command on each client node as well.

To run the DB2 Data Links Manager Administrator's db2profile or db2cshrc script file each time this user logs on to the system, add the following entry to the DB2 Data Links Manager Administrator's .profile script file:

   . INSTHOME/sqllib/db2profile (for bash, Bourne, or Korn shell)
   source INSTHOME/sqllib db2cshrc (for C shell)

where INSTHOME is the home directory of the DB2 Data Links Manager Administrator.

When you install DB2 Data Links File Manager using the software bundle feature, the DB2 Product Library (HTML) filesets are not automatically installed. Also, the DB2 Product Messages, other than in English, are not installed. You must install these filesets separately. For more information on how to install these filesets, refer to the DB2 for AIX server installation chapter in the DB2 for UNIX Quick Beginnings manual.

[ Top of Page | Previous Page | Next Page ]