Use of a data modeling tool to import DDL

Several types of data modeling tools are available. Some are mainframe-based and interact directly with Db2; others run on workstations or personal computers and communicate with Db2 only through DDL. Even for systems that run on the mainframe, the data structure design output from a data modeling tool is usually DDL.

To install an initial version of an application from a data modeling tool, you perform the following steps:

  1. Import the DDL to an alter-type work ID (using Import).
  2. Submit the work ID to generate a worklist (using Analysis).
  3. Execute the worklist (using Execution).
Warning

When you import DDL to a work ID, you lose any authorizations that are granted in the DDL file.

When you receive the DDL file for a new version of your application’s data structures, you can perform a change migration process by

  • Comparing the DDL to the previous version (DDL or baseline)
  • Evaluating the generated CDL
  • Importing the CDL to a work ID, running Analysis, and then running Execution

If the data modeling tool generates CDL, you need to evaluate, import, analyze, and execute the CDL.

Whenever you import a new or updated version of the data structures that are generated by the data modeling tool, establish one or more baselines to allow for recovery in case you discover errors.

Important

BMC AMI Change Manager for Db2 uses the term scope to mean the set of Db2 objects that are affected by an operation, where the operation can be migration, a comparison, or the establishment of a baseline. Although Change Manager selects structures using scope rules, the method of structure selection is sometimes different in the data modeling tool and yields a different set of objects. You should keep this difference in mind when you read this user guide or the documentation for a data modeling tool.


Related topic

Use-of-data-modeling-tools


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*