DB2 Connect User's Guide

Appendix E. Binding Utilities for Back-Level Clients

If you have remote clients from a previous release, you may need to bind utilities on these clients to the host or AS/400 database server:

If the old client was used with a previous release of DB2 Connect against the same host or AS/400 database server, you do not need to do any additional steps.
If the old client was not used with DB2 Connect (for example, if several OS/2 machines were connected with no connection to a host or AS/400 database server), do the following:
1. If you have any DB2 for OS/2 Version 1.0 or 1.2 clients, create a bind list file with the following lines:
  sqlabind.bnd+
  sqlueiwi.bnd+
  sqluigsi.bnd+
  sqluiici.bnd+
  sqluiict.bnd+
  sqluexpm.bnd+
  sqluimpm.bnd+
  sqlurexp.bnd+
  sqlarxcs.bnd+
  sqlarxrr.bnd+
  sqlarxur.bnd
  
  and copy each of these bind files from one of your clients to the DB2 Connect workstation.
2. If you have Client Application Enabler Version 1.0 or 1.2, create a bind list file with the following lines:
  db2ajgrt.bnd+
  db2clics.bnd+
  db2clpcs.bnd+
  db2clprr.bnd+
  db2clpur.bnd+
  db2ueiwi.bnd+
  db2uigsi.bnd+
  db2uiici.bnd+
  db2uiict.bnd+
  db2uexpm.bnd+
  db2uimpm.bnd+
  db2urexp.bnd
  
  and copy each of these bind files from one of your clients to the DB2 Connect workstation.
3. At the DB2 Connect server, bind each bind list file to each host or AS/400 database server database. Issue commands similar to the following:
```
   db2 connect to DBALIAS user USERID using PASSWORD
   db2 bind path@bindfile.lst blocking all
         sqlerror continue messages bindfile.msg grant public
   db2 connect reset
```
  where DBALIAS, USERID, and PASSWORD apply to the host or AS/400 database server database, bindfile represents the name of the bind list file, and path represents the location of the bind list file.
  You can use the grant option of the bind command to grant EXECUTE privilege to PUBLIC or to a specified user name or group ID. If you do not use the grant option of the bind command, you must GRANT EXECUTE (RUN) individually for each package.
  To find out the package names for the bind files, enter the following command:
```
   ddcspkgn @bindfile.lst
```

[ Top of Page | Previous Page | Next Page ]