Managing Model Objects › Impact Analysis › Understanding Model Object Usages

Understanding Model Object Usages

The usages for a model object are all the model objects that use it (or all model objects it is used by). In other words, usages for a given model object are the model objects that require it in order to be complete and are external to the model object. A model object's usages are sometimes referred to as using objects. The following diagram shows the possible usages for each CA 2E model object type:

For example:

• Database fields (FLD) can be used by database files (FIL) or functions (FUN). In turn, files can be used by access paths (ACP) and application areas (APP).
• Access paths (ACP) can be used by messages (MSG), arrays (ARR), functions (FUN), and other access paths (ACP).

Note: There is no direct relationship between fields (FLD) and access paths (ACP). In other words, a change to a field does not directly affect the access paths that use it.

For more information on the note and the possible ways a given model object type can be used by other model objects types, see the CA 2E Command Reference Guide.