A change management script is the set of changes
that you want to make to your database. Specifically, a change management
script is a script that describes specification resources, change
commands, and metadata about how that change will be implemented.
When you run your changes from a change management script,
you are issuing commands to change your DB2 database. You use the Change
Management Script Editor to work with change management
scripts and to deploy the changes to a DB2 database.
Figure 1. Issuing change commands from the Change
Management Script Editor.
The Change Management Script Editor presents
a consolidated way to work with changes. With the editor, you can
access all of the objects and actions that are relevant to the changes
that you want to make.
You can use the
Change Management Script Editor to:
- Change database objects, including migrating objects
between environments
- Create change commands such as CREATE, ALTER, or DROP commands
- View the objects that will be impacted by your changes
- Preview the commands that will be issued to the database
- Save commands to a script
- Create commands to preserve your data
- Migrate data between environments
- Create RUNSTATS commands
- Create flush package cache commands
- Rebind your application packages
- Create REORG commands
- Run change commands to change the database
- View messages about the commands that you issued to the database
- Undo your changes if necessary
Important: To use change management scripts and the
Change
Management Script Editor, the Database Change Management
feature of
Optim™ Database
Administrator must
be installed, and change management capability must be enabled. For
more information, see
Enabling change management capability.