- The data administrator updates the Host Encyclopedia by checking in the data maintenance subset.
If the subset is not checked in, developers can get only Read protection to newly added entity types and attributes. Read protection is not sufficient to create information views or expected effects.
Change any shared objects that Version Control does not handle.
- The data administrator performs any deletes using the Model Management facility on the Host Encyclopedia.
Deleting an entity type or attribute causes a cascade deletion that eliminates the data record or field.
- The model manager performs all planned migrations that are based on predefined aggregate sets.
- The data administrator checks out the data maintenance subset again to prevent a developer from accidentally changing the data model.
See the data maintenance subset definition in the Implement Change section.
- The DBA generates the DDL on the mainframe so that any mainframe databases can be updated to the latest table and column definitions and so that any test data is converted.
- The DBA uses Intelligent Regeneration to update only the host RI triggers that need updating.
- The data administrator creates the database and the RI triggers to ensure that workstation construction works.
- The data administrator runs a Delete report for each object that is deleted at the next data model change session.
- The project leader can use the list to make assignments for removing references to the objects.
- Inform the team (and other sharing project teams) of the status and any issues arising from the data model change.
- Project team members use Intelligent Regeneration to help them create a new version of the mainframe load modules.
Note: A change to the data model deletion rules require the regeneration of action diagrams that call RI modules, because they also contain some of the code that enforces RI.
