|
The name of the DRDA target collection (AS/400 library) where the Microsoft OLE DB Provider for DB2 should store and bind DB2 packages. This could be same as the Default Schema.
The Microsoft OLE DB Provider for DB2, which is implemented as an IBM DRDA application requester, uses packages to issue dynamic and static SQL statements. Package names are not restricted and can be uppercase, lowercase, or mixed case.
The OLE DB provider creates packages dynamically in the location to which the user points using the Package Collection property. By default, the OLE DB provider will automatically create one package in the target collection, if one does not exist, at the time the user issues their first SQL statement. The package is created with GRANT EXECUTE authority to a single <AUTH_ID> only, where AUTH_ID is based on the User ID value configured in the data source. The package is created for use by SQL statements issued under the same isolation level specified when calling the OLE DB ITransactionLocal::StartTransaction or ITransactionJoin::JoinTransaction methods, as well as when setting the ADO IsolationLevel property on the Connection object.
A problem can arise in multi-user environments. For example, if a user specifies a Package Collection value that represents a DB2 collection used by multiple users, but this user does not have authority to GRANT execute rights to the packages to other users (the PUBLIC group on the DB2 system, for example), the package is created for use only by this user. This means that other users may be unable to access the required package. The solution is for an administrative user with package administrative rights to create a set of packages for use by all users. (For more information, see Creating Packages for Use with the OLE DB Provider for DB2).
The OLE DB Provider for DB2 ships with a tool program for use by administrators to create packages. The Data Access Tool is used to create packages. This tool can be run using a privileged User ID to create packages in collections accessed by multiple users. This tool creates a set of packages and grants EXECUTE privilege on these packages to the PUBLIC group representing all users on the DB2 system. The packages (for more information, see descriptions under the isoLevel parameter of the OLE DB ITransactionLocal::StartTransaction or ITransactionJoin::JoinTransaction methods, as well as the ADO IsolationLevel property) created are as follows:
AUTOCOMMITTED package (MSNC001 is only applicable on DB2/400)
READ UNCOMMITTED package (MSUR001)
READ COMMITTED package, (MSCS001)
REPEATABLE READ package, (MSRS001)
SERIALIZABLE package (MSRR001)
Note that the AUTOCOMMITTED package (MSNC001) is only created on DB2 for OS/400.
Once created, the packages are listed in the DB2 (mainframe) SYSIBM.SYSPACKAGE, the DB2 for OS/400 QSYS2.SYSPACKAGE, and the DB2 Universal Database (UDB) SYSIBM.SYSPACKAGE catalog tables.
Note that when upgrading from SNA Server 4.0, any existing SNA 4.0 packages must be re-created using the Host Integration Server CrtPkg tool to make them compatible with Host Integration Server 2006. The package names changed from SNA Server 4.0.
This property is equivalent to the DBPROP_DB2OLEDB_PACKAGECOL OLE DB property ID. | 