Note: The user ID creating the Db2 packages must have BINDADD privileges on the database. Consult with your database administrator to ensure that you have the correct privileges.

To explicitly create Db2 packages, bind the appropriate package creation list files for your operating system on your database server (see the following table). When you bind the list files, if any Db2 packages exist, they will be replaced by the new packages. The list files create Db2 packages that contain 200 dynamic sections and are created in the NULLID collection.

Table 1. Db2 Package Creation List Files/Location
File Location
DDJDBC_LUW.lst installdir /DB2/bind/LUW
DDJDBC_400.lst installdir /DB2/bind/iSeries
DDJDBC_MVS.lst installdir /DB2/bind/zOS

To explicitly create Db2 packages:

  1. Copy the appropriate list (*.lst) and bind (*.bnd) files to a directory on the database server.
  2. From the directory on the database server where you placed the list and bind files, start the Db2 command-line utility.
  3. Using the Db2 command-line utility, connect to the database where you want to bind the packages using the following command: 
    connect to database_name user authorization_name using password

    where:

    database_name is the name of the database to which you are connecting.

    authorization_name is the name of the user you are authenticating to the server.

    password is the user’s password.

  4. Execute the Db2 bind command: 
    bind @ list_file grant public

    where list_file is the name of the list file you want to bind.