Since you will be accessing data managed by other systems, you will require a user ID and password so that you can be authenticated by the system. To obtain these, contact the administrator responsible for the system where the data resides.
In addition, to access the system, you will require authorization to access data objects on the target database server; for example, tables, views, and program packages. To obtain the appropriate authorization, contact your database administrator.
An additional DB2 security mechanism called binding allows database administrators to limit access to specific applications. This mechanism is used to build program packages or plans. The database administrator then grants authority to users to execute these packages.
If you will be running an application developed using embedded SQL, a package will be supplied with your application. You must bind this package to each database that the application will access. Package files are usually supplied with the .bnd file type. CLI/ODBC users do not bind individual applications; instead, they must bind the CLI/ODBC driver itself to each database that will be accessed.
To bind applications or the CLI/ODBC driver, you require the following privileges on each database:
If your database administrator will not grant you these privileges, another user (usually the administrator) must perform the required binds.