Kbase P26457: 4GL. When to use the NO-UNDO option.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
04/06/2003 |
|
Status: Unverified
GOAL:
4GL. When to use the NO-UNDO option.
FIX:
When a variable is changed in a transaction or sub-transaction that variable and all other variables in that procedure are written to the local before image (.lbi) file.
To reduce the overhead of this journaling, define variables as NO-UNDO when:
1. The variable represents a constant that will never change.
2. The variable is always initialized before it is used.
3. UNDO processing serves no useful purpose.
4. The variable is changed in a loop that an error may not occur in.