The LIMIT ABORT_EXECUTION pragma controls the use of resources during the processing of an SQL statement. This pragma allows you to systematically provide statements with a local stop criterion. This local stop criterion is more restrictive than the global stop criterion ABORT-EXECUTION required for complex batch programs. ABORT-EXECUTION is set using RETRIEVAL-CONTROL or MODIFY-RETRIEVAL-CONTROL.
The local stop criterion set using LIMIT ABORT_EXECUTION
is only valid for the current request.
cannot be overridden by MODIFY-RETRIEVAL-CONTROL.
has no effect if the pragma is not in a “searching“ statement.
has no effect if the value has been specified as 0 or the specified value is greater than that of the global stop criterion. In this case the value of the global stop criterion applies.
If several LIMIT ABORT_EXECUTION pragmas are specified in one request, the last valid pragma value will apply. If no LIMIT ABORT_EXECUTION pragma is specified, the global stop criterion will apply.
In a sequence of DECLARE CURSOR, OPEN and FETCH statements, the pragma must be specified in the DECLARE CURSOR statement. Its effect depends on the search path selected, but only when the OPEN or FETCH statement is executed.
The pragma can also be used in CALL and in routines, see section "Pragmas in routines" .
LIMIT ABORT_EXECUTION block_access
block_access
This argument allows you to specify the number of logical block access instances. Once this number has been reached, no more hits will be detected and the statement will be terminated. The number of block access instances should be specified as an unsigned integer ranging from 0 to 2147483647.