If you have remote clients from a previous release, you may need to bind utilities on these clients to the DRDA server:
sqlabind.bnd+ sqlueiwi.bnd+ sqluigsi.bnd+ sqluiici.bnd+ sqluiict.bnd+ sqluexpm.bnd+ sqluimpm.bnd+ sqlurexp.bnd+ sqlarxcs.bnd+ sqlarxrr.bnd+ sqlarxur.bndand copy each of these bind files from one of your clients to the DB2 Connect workstation.
db2ajgrt.bnd+ db2clics.bnd+ db2clpcs.bnd+ db2clprr.bnd+ db2clpur.bnd+ db2ueiwi.bnd+ db2uigsi.bnd+ db2uiici.bnd+ db2uiict.bnd+ db2uexpm.bnd+ db2uimpm.bnd+ db2urexp.bndand copy each of these bind files from one of your clients to the DB2 Connect workstation.
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 DRDA server database, bindfile is the name of the bind list file,
and path is 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