A CA 2E file is similar to an i OS file in the sense that it is a list of fields. A CA 2E file is different from an i OS file because it has relations specified for it. These relations specify referential integrity checks to be performed in the functions that use the file. The i OS Database Manager does not perform referential integrity checks between database files.
CA 2E creates the necessary source code to perform referential integrity checking. This is validation of the relations between files. As an example, use the entity Employee is Owned by the entity Company. When a Company Code is associated with an Employee Code, CA 2E checks to ensure that the Company Code exists in the Company file.
CA 2E lets you specify whether or not these integrity checks should be performed. This is done by specifying whether the relation is mandatory or optional. If the relation is mandatory, the end user will have to enter a valid value in the foreign key field. If the relation is optional, the end user has a choice whether to enter a value; however, the value entered must be valid.CA 2E also lets you specify your own checking process if you desire.
See the chapter "Modifying Device Designs" in Building Applications for more information on mandatory and optional checking.
|
Copyright © 2014 CA.
All rights reserved.
|
|