If a serious database error occurs, such as LOG FULL, DATABASE FULL, the load run is implicitly aborted and those counter readings are recorded which represent the state of the transaction most recently committed.
If the run has been aborted implicitly, LOAD informs the user on the screen about the cause of the error and then ends the current LOAD session.
The recorded counter readings allow an aborted run to be continued (after having removed the cause of the error, if any) with
==> RUN FROM n
where n is the number of the first row that has not yet been processed. Therefore, interrupted load runs need not be completely repeated.
With various options of the RUN command, the user himself can determine when the run is to be terminated. If a load run is started, e.g., as follows
===> RUN FROM 1 FOR 100
the first 100 rows of the input file are loaded and then the run is terminated, independent of the number of inserted and rejected rows.
Interactive load runs are interrupted when a certain number of rows have been rejected. A special screen is displayed with several options, one to terminate the run. The number of inserted rows is not taken into consideration when deciding to interrupt or not.