Table Map

The following panel is displayed:

Source 1

Different rules are used for populating the CID (default Creator ID) and Table Name values based on the source types. For Source 1, CID is populated with the Default Creator ID from the Extract File or Access Definition. In addition, all table names from the Extract File or Access Definition are filled in as the Source 1 tables. These values are protected.

Source 2

For Source 2, if the source type is an Extract File or Access Definition, CID is populated appropriately from the named source. The Table Name values are populated with only the table names from Source 2 that match table names in Source 1. The remaining values are blank.

If the source type is All Rows in Multiple Tables (as in this example), then the Src 2 CID and Table Name values are populated with the same values as their Source 1 counterparts.

Specifying CID

If Source 2 is All Rows, you can overtype the CID as desired. For this sample, assume the default Creator ID is FOPDEMO.

Specifying Table Names

You can edit the table names directly or request a selection list of available tables not currently mapped as Source 2. When editing names, you can use the CLEAR command to remove all Source 2 names before typing names on the panel. You can also prefix or suffix the Source 2 names with a string of your choice.

Use the LIST TABLES command to display a selection list of tables and automatically insert your selection as the Source 2 table name. The APPLY command overlays all or part of the displayed Table Map with the specifications from a stored Table Map. (For details about defining and storing Table Maps, see the Common Elements Manual.)

You can also replace the initial table names with an existing Table Map. In addition to Table Maps, you can specify Column Maps to map the columns for a pair of tables that do not have matching names provided they have compatible data types. You can also eliminate columns from the comparison. You can define a Column Map for the current Compare Definition only (referred to as LOCAL) or a Column Map that is stored in the Optim™ Directory and reusable. (For details about defining and storing Column Maps, see the Common Elements Manual.)

For this sample, the tables and column names are the same and all tables and columns are to be compared. Column Maps are not needed.

When the Table Map specifications are complete, use END to proceed.

Relationships

When comparing two sets of data from multiple tables, the relationships used to determine the related changes are important. Only one relationship may be selected between any two tables in a given direction (that is, for a specific parent and child), regardless of the relationships used to extract the data. In this example, only one relationship is defined between these tables; therefore, Compare will automatically use the appropriate relationships.