112 DB2 for z/OS Administration Tools for Enhanced Change Management
4.1 General considerations
Before you start learning about Change Management, we want to make you aware of some
general topics that might help you in understanding Change Management.
Many panels within Change Management are defined with point-and-shoot capability. You
can position your cursor at those fields (by using the Tab key) and press Enter; this has the
same effect as typing the command directly as a line command. For instance, the line
commands CONTINUE and SAVE are probably the most frequently used candidates for
point-and-shoot. Use the Tab key to position the cursor under the word (such as CONTINUE)
and press Enter. This is the same as keying in the word CONTINUE on the command line.
4.1.2 Data sets
Many data sets are created during your use of the products Admin and Compare, which
allocate libraries always with SMS defaults. Check your libraries being allocated to make sure
that they do not belong to default management classes. If so, add appropriate ACS routines to
4.1.3 Version files
An important part of the product is based on versions; they are discussed in detail in this
book. You might experience some confusion in terms of version terminology in the official
literature. In previous days of DB2 Admin and DB2 Compare, versions already existed. They
were saved in a data set and the terminology
version file became a standard. These files can
grow large in size, and some customers have found disk space relief by allocating those files
to a data class that invokes SMS compression functions. They have also reduced elapsed
time by explicitly specifying more I/O buffers.
With the introduction of Change Management, versions can now be stored within the Change
Management database. But you might find that those versions stored internally in a DB2 table
of the Change Management database are called
version files anyway, although there is no
connection to a data set.
Versions can be created in one of three ways:
When using CM, you can define a version scope (which includes the objects to be
included in a version) and then use the GV line command on the Version Scope panel to
generate a version based on the scope.
When running a change in CM, you can request a version of the objects be generated
after the changes have been applied.
When using DB2 Object Comparison Tool, you can have versions of the source and target
objects generated (these are the versions saved as a data set). When CM is enabled, you
have the option of storing versions in data sets or in the CM database.