DB2 Version 9.7 for Linux, UNIX, and Windows

CLI bind files and package names

CLI packages are automatically bound to databases when the databases are created or upgraded, or a fix pack is applied to either the client or the server. If a user has intentionally dropped a package, then you must rebind db2cli.lst.

Rebind db2cli.lst by issuing the following command:

Linux and UNIX

db2 bind BNDPATH/@db2cli.lst blocking all grant public

Windows

db2 bind "%DB2PATH%\bnd\@db2cli.lst" blocking all grant public

The db2cli.lst file contains the names of the required bind files for CLI to connect to DB2® servers on Linux, UNIX, and Windows (db2clipk.bnd and db2clist.bnd).

For host and IBM® Power Systems™ servers use one of ddcsvm.lst, ddcsmvs.lst, ddcsvse.lst, or ddcs400.lst bind list files.

Warnings that are generated when binding CLI packages (such as db2clist.bnd or db2cli.lst) to workstation or host servers are expected. This is because DB2 database systems use generic bind files, but the bind file packages for CLI packages contain sections that apply to specific platforms. Therefore, a DB2 database system might generate warnings during the binding against a server, when it encounters a platform-specific section that does not apply to the server.

The following is an example of a warning that can be ignored which might occur when binding a CLI package (such as db2clist.bnd or db2cli.lst) to a workstation server:

LINE    MESSAGES FOR db2clist.bnd
------  --------------------------------------------------------------------
  235   SQL0440N  No authorized routine named "POSSTR" of type 
                  "FUNCTION" having compatible arguments was found.  
                  SQLSTATE=42884

Table 1. CLI bind files and package names
Bind file name	Package name	Needed by DB2 servers on Linux, UNIX, and Windows	Needed by host servers	Description
db2clipk.bnd	SYSSH`xyy`	Yes	Yes	dynamic placeholders - small package WITH HOLD
	SYSSN`xyy`	Yes	Yes	dynamic placeholders - small Package NOT WITH HOLD
	SYSLH`xyy`	Yes	Yes	dynamic placeholders - large package WITH HOLD
	SYSLN`xyy`	Yes	Yes	dynamic placeholders - large package NOT WITH HOLD
db2clist.bnd	SYSSTAT	Yes	Yes	common static CLI functions
db2schema.bnd	SQLL9`vyy`	Yes	No	catalog function support
Note: 'S' represents a small package and 'L' represents a large package 'H' represents WITH HOLD, and 'N' represents NOT WITH HOLD. '`v`' represents the DB2 server version: for example, E=Version 8, F=Version 9 '`x`' is the isolation level: 0=NC, 1=UR, 2=CS, 3=RS, 4=RR '`yy`' is the package iteration 00 through FF '`zz`' is unique for each platform For example, for the dynamic packages: SYSSN100 A small package (65 sections) where all cursor declarations are for non-held cursors. Bound with isolation level UR. This is the first iteration of that package. SYSLH401 A large package (385 sections) where all cursor declarations are for held cursors. Bound with isolation level RS. This is the second iteration of that package. Previous versions of DB2 servers do not need all of the bind files and will therefore return errors at bind time. Use the bind option SQLERROR CONTINUE so that the same package can be bound on all platforms and errors will be ignored for any statements not supported there.

db2schema.bnd bind file

The db2schema.bnd bind file is automatically bound when the database is created or upgraded, or a fix pack is applied on DB2 servers on Linux, UNIX, and Windows, and exists only on these types of servers. This bind file is located at the server and should be bound manually (from the server), if the package was intentionally dropped by a user or if an SQL1088W (+1088) warning is received after database creation or upgrade.

Only the most recent version of this package is needed.

If the package is missing, it must be rebound locally on the server. Do not bind this package against remote servers (for example, against a host database). The bind file is found in the sqllib/bnd directory of the instance home directory, and is rebound with the following command:

bind db2schema.bnd blocking all grant public

If an SQL1088W warning was received after database creation or upgrade, and the db2schema.bnd package is missing, increase the applheapsz database configuration parameter to 128 or greater, and attempt to rebind. No errors should be reported during binding.