Using CA OLQ Efficiently › Controlling Data Retrieval › Interrupt count

Interrupt count

What is the interrupt count?

The interrupt count is the number of CA OLQ database requests allowed before execution is interrupted. When interruption occurs, you can choose to resume execution or to halt execution. This interruption allows you to monitor processing during retrieval.

When processing is interrupted, CA OLQ displays this message:

OLQ 098006 00  50 whole lines and 0 partial lines in report.
OLQ 098007 00  50 records read.   50 records selected.
OLQ 098009 00  Continue (yes/no)?

Primary function:

The primary use for interrupt count is to specify the number of CA OLQ database requests after which CA OLQ interrupts the processing. This enables you to limit CA OLQ database requests.

Additional use:

Another use for interrupt count is to determine the number of rows CA OLQ saves in a table before it performs a commit. (When CA OLQ performs a commit, database locks are released.)

Note: Keep in mind that, when any problems occur with saving data, CA OLQ rolls back to the last commit. You could end up with a partial table. (This applies to both SQL and ASF tables.)

Setting interrupt:

You initially set the interrupt count during system generation with the ADD/MODIFY OLQ statement:

INTERRUPT COUNT IS nnn
MAXIMUM INTERRUPT COUNT IS nnn

These statements set the default interrupt count and the default maximum interrupt for CA OLQ. In this way, you can limit the number of database calls performed on each retrieval request. The system default set at installation is 100. You can, however, make this number as large or as small as you wish. To keep CA OLQ from performing commits while saving tables, set the interrupt count to zero.

A user can retrieve records without specifying an interrupt count; the interrupt count set during system generation acts as the default. If a user uses the SET INTERRUPT COUNT (in CA OLQ) to specify a count that is higher than the maximum set during system generation, the count defaults to the count set with the MAXIMUM INTERRUPT COUNT IS statement during system generation. To prevent CA OLQ from performing commits, set the interrupt count to zero. Note that even when the interrupt option is off, the interrupt count is still set.