Previous Topic: What to Generate/Compile When You Change a Model ObjectNext Topic: Finding Where CA 2E Objects are Used

Generating and Compiling Your Application › Generating and Compiling After Changes › Changes Requiring Generation/Compilation

Changes Requiring Generation/Compilation

Following is an overview of dependent model objects that require generation and compilation as a result of changing various model object types:

If You Changed

You Must Generate and Compile

Function options

The function

Device design

The function

Action diagram

The function

Note: For a non-generated (internal) function, all functions referencing that function must be generated/compiled.

Function message

If parameters in a message are changed, all functions using the message. If no parameters have changed, no generation or compilation is needed.

Function parameters

The function and any other functions that use it.

Note: If you changed or added parameters, you must first revisit each reference to the function in the action diagram, supplying the new parameters. Use Find Error within an action diagram to find where the new parameters are missing.

Access paths

All functions using the access path and all associated access paths.

Note: Use function references (F next to an access path).

Condition value

All functions referencing the condition value.

Notes:

If the condition value is used in select/omit logic on an access path, generate/compile that access path.

If only the condition value is changed, you do not need to generate/compile the function(s) using the access path.

If you change the values list prefix, you must generate/compile all programs that call the values list display program

YDATGEN

model value

Compile all functions.

Note: Set YDATGEN to VRY (display/enter date in MDY), then you can make changes at execution time.

Relation

If the relation is changed:

All access paths and all functions using those access paths.

All access paths that include the changed relation as a foreign key. For example, if the key of a referred to file changes, the files that refer to the relation are affected. This, in turn, triggers function changes.

All files, all access paths, and all functions using those files.

If the relation is added or deleted, all files using the relation, all access paths, and all functions using those files.

The only time you do not need to regenerate access paths and functions following a change to a file (FIL) is if the access path does not include the changed relation.

The following table shows some examples of changes to files that determine whether you need to generate and compile functions.

File

Format Before

Field Length

Format After

Field Length

Recompile Function?

A

FLD1

FLD2

3.0

2

FLD1

FLD2

3.0

2

No

B

FLD1

FLD2

3.0

4

FLD1

FLD2

3.0

2

Yes

C

FLD1

FLD2

3.0

2.0

FLD1

FLD2

3.0

2

Yes

D

FLD1

FLD2

3.0

2

FLD1

FLD2

FLD3

3.0

2

5

Yes

E

FLD1

FLD2

FLD3

3.0

5

2

FLD1

FLD2

3.0

2

Yes