Some bind options might
not take effect when binding CLI packages
with the following list files: db2cli.lst, ddcsmvs.lst, ddcs400.lst, ddcsvm.lst,
or ddcsvse.lst.
Because CLI packages
are used by CLI,
ODBC, JDBC, OLE DB, .NET, and ADO applications, any changes that you
make to the CLI packages
affect all applications of these types.
Therefore, only a subset of bind options are supported
by default when binding CLI packages.
The supported options are: ACTION, COLLECTION, CLIPKG, OWNER, REPLVER,
and GENERIC. All other bind options that impact CLI packages
are ignored.
To create
CLI packages
with bind options that are not supported by default, specify the
COLLECTION bind
option with a collection ID that is different from the default collection
ID, NULLID. Any bind options specified are then accepted. For example,
to create
CLI packages
with the
KEEPDYNAMIC YES bind
option, which is not supported by default, issue the following command:
db2 bind @db2cli.lst collection newcolid keepdynamic yes
In order for CLI/ODBC
applications to access the CLI packages
created in the new collection, set the CurrentPackageSet CLI/ODBC
keyword in the db2cli.ini initialization file
to the new collection ID.
To overwrite
CLI packages
that already exist under a particular collection ID, perform either
of the following actions:
- Drop the existing CLI package
before issuing the bind command for this collection ID.
- Specify the ACTION REPLACE bind option when issuing
the bind command.