292 DB2 for z/OS Administration Tools for Enhanced Change Management
6.2 Modifying the Master Development Database (D0) using
generated DDL and Object Compare
Some very important functions in a computer facility are creating new objects or making
enhancements to existing objects. These changes normally move from the development
system to the test system and are eventually implemented in multiple production sites. After
the changes are made to the objects, you can now use DB2 Object Compare and CM to
manage, track, synchronize, and carry out the changes.
Object Compare can use any of these sets of items:
򐂰 Two base version files
򐂰 Two DDL files
򐂰 Two catalog objects
򐂰 One DDL file and one catalog object
The use of ignore files and mask files can be used during the Object Compare process, which
creates the Compare. The source and target files can be objects within the same system, like
a development system. Another way to use Object Compare is to compare source and target
files between two systems with source being the development objects and target being
production system objects.
When using two different system objects, you would be doing a PROMOTE process and
using OC to create a delta data set, which is made available from the Dev system (source) to
the target system (that is, Test, Production) for the import data. Once the import is completed
on the target system, the delta file (consisting of the changes) is registered in CM on the
target system and can be analyzed and run to promote the changes to the target system
objects.
We highly recommend following careful planning and change management strategies. Some
database changes can have cascading effects on application performance and can be difficult
to find and correct. The new CM process provides an interface to manage all of the version
files for a database and allows you to track the history of changes. The use of change owner
for every piece of work can provide a method for maintaining a relationship between version
files, mask files, ignore files, generated DDL, and unloaded data. The DBA can query, check,
track, and find all of the components involved in the changes.
6.2.1 Making changes to the database
Changes can be both logical and physical to the database implementation. You can create
your own DDL or use DB2 Admin to create the DDL.
A few examples of
logical changes to a database would be a change to the column name,
length, or type.
A few examples of
physical changes would be a change of a segmented table space to a
partitioned table space, or a column added to a table, or non-compressed table space to a
compressed table space, index changed from CLOSE YES to CLOSE NO, and adding a
TRIGGER.

Get DB2 for z/OS Administration Tools for Enhanced Change Management now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.