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.

LS1				.	Automatic commit will
	LS2	(LSupdate)			occur on completion of
	read	FILE1	FILE2		LS2 since it is an
	write	FILE1			LSUPDATE

	LS3
	read	FILE3	FILE4
		LS4
		read	FILE5		Automatic commits will
		write	FILE5		occur after each iteration
	write	FILE3	FILE4		of LS3
					Automatic commit will
	LS5				occur when function
					ends
LS6	(called)				Automatic commits occur after each iteration of LS6 when committable, which it is if called from LS1 or LS5 but not from LS2, LS3 or LS4
read	FILE6	FILE7

Comment on this topic

Topic ID: 720205