Version scopes
A version scope defines the set of objects to include in the processing of a version.
A version scope determines the objects that are included in a version.
A version scope can be any set of objects, such as one or more databases, or a group of table spaces. Typically, you want to define scopes that identify all of the objects for an application or application area. For example, the scope for a human resources application should contain all the human resource databases.
After you create a version scope, you can create a base version for that set of objects.
A version scope must exist if you plan to create a new base version when you apply changes. If you have a new base version created when you run a change to reflect the object definitions after the changes, you must specify the version scope for the version.
Maintaining a version scope is a manual process, and you should ensure that the definition of the scope always includes all of the objects that you intend. For example, assume that you defined version scope SCOPE1 to include databases DB01 and DB02 and then created version BASE1. Later, you run CHANGE1, which creates a table in DB01 and creates a new database DB03, specifying to create a new base version BASE1 using SCOPE1. Database DB03 is not automatically added to SCOPE1.
DB2 Admin ------------------- CM - Manage Versions ---------------------- 16:59
Option ===>
1 - Display versions DB2 System: DD1A
2 - Display version scopes DB2 SQL ID: ADM001
3 - Insert a version scope
4 - Import version file
Enter display selection criteria (Using a LIKE operator, criteria not saved):
Name . . . . . . . > Created by . . >
Owner . . . . . . > Altered by . . >
Created within . . Version ID . .
Altered within . .
From the Manage Versions panel, you can display the existing version scopes to work with them or create a new version scope.