Report and Update Functions |
Virtual Machine |
 |
|
Report and Update Functions |
Virtual Machine |
|
By default, automatic commits are scheduled on completion of a committable Report or Update cycle. At any given time, there is at most one committable Report or Update cycle, defined as the least-nested Report and Update cycle in execution with file specifications. Since it is not currently possible to define a Report or Update without file specifications, LR/LU1 is always the committable Logical Report and Logical Update cycle.
The following exceptions apply:
An automatic commit occurs after a file is cleared.
An automatic commit will also occur at the end of the function. Note that this differs from completion of cycle, which would be bypassed by an FNEXIT statement in logic.
|
|
|
|
|
|
|
|
Automatic commits will occur |
Clear |
FILE2 |
FILE4 |
|
|
|
|
|
after each file is cleared |
|
|
|
|
|
|
|
|
|
Cycle[1] |
|
|
|
|
|
|
|
|
read |
FILE1 |
FILE2 |
|
|
|
|
|
|
|
Cycle[2] |
|
|
|
|
|
|
|
|
read |
FILE3 |
FILE4 |
|
|
|
|
|
|
write |
|
FILE4 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Cycle[3] |
|
|
|
|
|
|
|
|
read |
FILE5 |
|
|
|
|
|
|
|
|
Cycle[4] |
|
|
|
|
|
|
|
|
read |
FILE6 |
|
|
|
|
|
|
|
write |
FILE6 |
|
|
|
|
Automatic commit will occur |
|
write |
FILE5 |
|
|
|
|
|
on completion of Cycle[1] and |
write |
FILE1 |
FILE2 |
|
|
|
|
|
when the function ends |
|
|
|
|
|
|
|
|
|
Cycle[5] |
(called) |
|
|
|
|
|
|
|
read |
FILE7 |
FILE8 |
|
|
|
|
|
|
write |
FILE7 |
|
|
|
|
|
|
|
Topic ID: 720191