A deployment script describes specification resources, change
commands intended to implement the change, and metadata about how that change
will be issued.
In other words, the deployment script is the set of changes that you want
to make to your database. When you deploy your changes from the deployment
script, you are issuing commands to change your DB2 database. You can use
the Deployment Script Editor to deploy your changes to a DB2 database.
Figure 1. Deploying change commands from the Deployment
Script Editor.
The Deployment Script Editor presents a consolidated way to work with the
change that you want to deploy. It allows you to access all of the objects
and actions that are relevant to the change that is being deployed.
Within the Deployment Script Editor you can:
- Specify your database connection information
- Edit your target physical data models
- Compare the base and target models
- Migrate objects from other databases to the target model
- Create change commands, edit existing change commands, and import other
change command files
- Create export and import commands to preserve your data
- Migrate data between environments
- Create runstats commands
- Create flush package case commands
- Rebind your application packages
- Create REORG commands
- Preserve authorizations
- Refresh your base model
- Deploy your changes to the DB2 catalog
- Undo your changes