To prevent Quantum from checking array boundaries during a run, type:

at or near the start of the edit.

Quantum normally terminates if it detects that you are writing beyond the end of an array. For example:

This example defines an integer array called ‘number’ as having 10 cells. When Quantum reads the assignment statement and detects that it refers to ‘number(11)’ it will terminate because there are only 10 cells in the array, not 11. The same would be true for statements which referred to, say, t201 when the size of the T array had not been extended past the default of 200 cells.

The exceptions to this are emit, delete, partial column moves and reads from fetch files. For more information about fetch files, see The fetch statement.

While they might save time in the long run, these checks mean that a job runs slightly slower than it otherwise would.

To run without these checks, insert a nobounds statement near the start of the edit.