Assimilation › Assimilation Procedure

Assimilation Procedure

Use the following procedure to perform assimilation.

1. Retrieve existing i OS physical files using the YRTVPFMDL command. This command allows you to retrieve (the definitions of) one, several, or all i OS physical files in the database.

You can specify a value for the RMVFLDPFX parameter of the command to indicate whether or not you want CA 2E to drop the prefix from the DDS field names in the retrieved file. The purpose of using this parameter is to make sure the DDS names match those of your existing programs.

For more information, see the section Changing Field Name and Attribute Type.

2. Identify key fields. You identify key fields to CA 2E by changing the relevant Has relations into Known by relations since all fields are assimilated as Has relations.

3. Adding file-to-file relationships. You change or add new relations to explicitly indicate file relationships to include the processing logic for the keys arising from Owned by or Refers to relations, and for referential integrity checking.

If adding a relation causes a mismatch between the sequence of the fields you defined to CA 2E and those of the existing i OS physical file, you can change the sequence number using the Edit Physical File Format Entry panel. For example, if a Known by relation causes the field to be defined as one of the first fields in the file, change the sequence number using the Edit Physical File Format Entry panel.

4. Lock the physical file. You lock the physical file in your model to prevent inadvertently selecting the existing file definitions for recompilation.

For more information on:

• Physical files, see the Building Access Paths chapters "Adding Access Paths" and "Tailoring For Performance"
• How to lock files, see the chapter "Using Your Model" in the Administration Guide