You can transform the complete Data Model or a portion of it. Use the Diagram and Open options to control the data structure definition that is created during the Transformation Process to select the DB2 z/OS Technical Design defaults. In general, the TD defaults do not need adjusting. Review them with a Database Administrator (DBA) before implementation on the host.
You cannot use some words as ordinary identifiers in a context in which they could be interpreted as SQL keywords. For example, you cannot use COUNT as a column name in a SELECT statement. You can use words as an ordinary identifier in other context. In the statements where the word can never be an SQL keyword, you can use the word as a delimited identifier in context. For example, when double quotation marks (") begin and end delimited identifiers, as in "COUNT". You can use "COUNT" as a column name in a SELECT statement. For a complete list of Reserved Words, see the IBM documentation for DB2.
During Transformation, CA Gen attempts to use the TD names that are specified in the Data Model for data definition components. When CA Gen detects a name that violates the DBMS reserved word conventions and Reserved Word Support is set to YES, CA Gen automatically changes the name to a non-reserved word.
Plan a partial Transformation carefully to avoid problems during system generation. For example, transform all entities that are referenced by the business system you intend to generate. It is possible to forget to transform entities that are not directly referenced by the action diagrams for the business system, but referenced by the generated code.
As an example, when implementing referential integrity, the generated code includes referential integrity logic for mandatory relationships. The logic reference entities that are not directly referenced by the action diagrams. These entities must be transformed for successful system generation.
Similar problems occur if you change the Data Model after transformation. The impact of changes to the Data Model is not always obvious, and a partial retransformation cause inconsistencies. Perform a consistency check on the Data Store List and Data Structure List to detect these inconsistencies after a partial transformation or retransformation. The When Changed Report can help in planning a partial transformation.
Note: For more information, see the Host Encyclopedia User Guide.
For DB2 applications, identify the DB2 subsystem in which the generated application runs before creating the DDL.
After Transformation, when you change the Data Model, make an associated TD change to maintain consistency. Keep the TD synchronized with the Data Model by running transformation. When you run transformation, it replaces the initial database design, including changes that are made and creates a database design. It deletes a relationship triggers and adds new ones.
To leave the previous database design triggers intact and change only what is inconsistent or incomplete, use the Retransformation option.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|