The following terms are related to the DB2 Package Bind Option:
An individually bound DBRM.
The database server's unique name. An application uses location to access a DB2 database server. The application can use a database alias to override the location name when accessing a remote server.
A logical grouping of packages. The collection identifier (ID) is part of the package name. The collection is not a physical entity. DB2 uses the collection ID to allow a plan to reference multiple packages by a single identifier. Specify the collection ID on one of the bind options panels to do package binding.
Input to a plan bind that defines the search order that DB2 is to use when looking for packages. It can include specific package names, or a collection ID with a wildcard (collection_ID.*) for the package ID. In the latter case, the entire collection is searched for a match on package ID and consistency token. Collection_ID can be qualified with a location also, for example, location.collection_ID.
An identifier that differentiates between two precompilations of the same source member at different points in time. It can be anything meaningful to the user such as TEST and PROD or Release 1, and Release 2. Version allows a collection to include more than one package with the same name. The package that is used is always the one with the matching consistency token. Version allows easy backout of changes. This can also be done without version by using more than one collection.
The package owner's authorization ID.
Implicit the qualifier for the unqualified table, view, index, and alias names in the static SQL statements of the package.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|