4.9.4 When To Recompile
This chart summarizes when you will be required to make the physical file, the logical file and the OAM operational after making a specific change.
Trigger functions are included in the chart because they might need to be recompiled more frequently than 'normal' functions. The file level trigger functions have a list of the fields in the file, in the correct order, including virtual fields. If anything like field type, length, order of fields, etc. changes, the trigger must be recompiled.
Trigger functions and normal functions may or may not require a recompile, depending on how the functions use the changed fields. This is indicated with 'O' for Optional.
Note: A trigger and a trigger function are not the same thing. A trigger is the definition of when a function will be called. It consists of trigger points, trigger conditions and the name of the trigger function. A trigger function is an RDML coded program that defines the action to be taken.
|
Type of Change |
Physical File |
Logical File |
OAM |
Trigger Function |
Function |
Detected |
|
Field Length/Type |
Y |
Y |
Y |
Y |
O |
Y |
|
Column Heading/Label |
N |
N |
N |
O |
O |
- |
|
Edit code/word |
N |
N |
N |
O |
O |
- |
|
Default Value |
N |
N |
Y |
O |
O |
N |
|
Output Attribute |
N |
N |
Y |
O |
O |
N |
|
Display Attribute |
N |
N |
N |
O |
O |
- |
|
Prompt |
N |
N |
N |
N |
N |
- |
|
Help Text |
N |
N |
N |
N |
N |
- |
|
Authority |
N |
N |
N |
N |
N |
- |
|
Validation Rules |
N |
N |
Y |
N |
N |
Y |
|
Virtual Fields |
N |
N |
Y |
O |
O |
Y |
|
Batch Control |
N |
N |
Y |
N |
N |
Y |
|
Access Routes |
N |
N |
N |
N |
N |
Y |
|
Logical File |
N |
Y |
Y |
N |
N |
Y |
|
Physical Files |
Y |
Y |
Y |
O |
N |
Y |
|
Trigger Point |
N |
N |
Y |
O |
N |
Y |
|
Trigger Condition |
N |
N |
Y |
N |
N |
Y |
Refer to the LANSA Web site technical support pages (www.lansa.com/support) for more details.