- Screen Functions

By default, automatic commits are scheduled after each iteration of a committable cycle. At any given time, there is at most one committable cycle, defined as the least-nested cycle in execution with file specifications.

The following exceptions apply:

For committable Update cycle, a commit occurs only after the last iteration. The behaviour for Update cycle is consistent with that for an Update cycle in an Update function.
When a new page is to be displayed in a committable Paging Cycle, the processing required to generate the page (typically several iterations of the cycle), is contained in one transaction.
When deleting records in a committable Paging Cycle, selection processing (which may involve several pages) remains a single transaction until the deletion is activated or cancelled.
An automatic commit occurs at the end of the function.

Cycle1					Automatic commit will
	Cycle2	(Cycleupdate)		occur on completion of
	read	FILE1	FILE2		Cycle2 since it is an
	write	FILE1			CYCLEUPDATE

	Cycle3
	read	FILE3	FILE4
		Cycle4
		read	FILE5		Automatic commits will
		write	FILE5		occur after each iteration
	write	FILE3	FILE4		of Cycle3
					Automatic commit will
	Cycle5				occur when function
					ends
Cycle6	(called)				Automatic commits occur after each iteration of Cycle6 when committable, which it is if called from Cycle1 or Cycle5 but not from Cycle2, Cycle3 or Cycle4
read	FILE6	FILE7

Comment on this topic

Topic ID: 720205