| Product: | DB Connectivity ODBC, OLE DB and .NET (Ritmo) Products for Db2 LUW and mainframe |
| Version: | All |
| ID: | 1043 |
| Summary: | Package names and authorities for DB Connectivity drivers/providers packages on IBM Db2 for LUW or mainframe only |
DB Connectivity drivers and providers initially create packages that are subsequently re-used. You can specify where to create the package in the Data Tab of the data source/data link configuration. Package Collection indicates in which schema the package will be stored.
Default Package Names (based on isolation level and hold cursor on commit option):
ODBC/OLE DB
| Isolation Level | hold cursor off | hold cursor on | |
| NC No Commit 0 | HITPKG0 | HITPKG0H | |
| RS Read Stability 1 | HITPKG1 | HITPKG1H | |
| UR Uncommitted read 2 | HITPKG2 | HITPKG2H | |
| CS Cursor Stability 3 | HITPKG3 | HITPKG3H | default |
| RR Repeatable Read 4 | HITPKG4 | HITPKG4H |
Ritmo
| Isolation Level | hold cursor off | hold cursor on | |
| NC No Commit | HITR30C0 | HITR30H0 | |
| RS Read Stability | HITR30C3 | HITR30H3 | |
| UR Uncommitted read | HITR30C1 | HITR30H1 | |
| CS Cursor Stability | HITR30C2 | HITR30H2 | default |
| RR Repeatable Read | HITR30C4 | HITR30H4 |
You should specify a collection or schema and create a package. You need to grant access to this package to the user that will connect with driver/provider.
To create the package automatically:
- Connect to the Db2 database using the Test option in the Toolbox.
- Specify a user who has permission to create packages in the collection you have chosen.
- Modify the permissions on Db2 so that all users can access and modify the package.
GENERAL PACKAGE INFORMATION
The driver/provider uses the authority of the user specified in the login/password pair to perform the bind package operation.
For Db2 on z/OS (OS/390, MVS) or Db2 LUW (on LINUX, UNIX, Windows), you need to log in using either SYSADM or SYSCTRL, or have an account with privileges to run BINDADD and CREATE IN COLLECTION your-collection. You need the CREATE IN authority only if you only have the BINDADD authority.
The CREATE IN COLLECTION and BINDADD privileges are needed for the initial connection from the driver. Once the package is created and statements are bound, subsequent users do not need these privileges. The packages are created in a collection as specified in the "Package Collection" field, so the privileges must be related (at least) to that collection.
To set authorities for a specific user, type the following at a Db2 command prompt:
GRANT CREATETAB,
BINDADD, CONNECT ON (database name) TO USER (username )
Replace (database name) with the actual name of the Db2 database you are accessing and replace (username) with the name of the user ID that you will be logging on with when using the driver/provider.