<< Click to Display Table of Contents >> Navigation:  User guide > Errors > Errors

If a run does not complete as expected then check the Log file and check the dates on the output files.

The Control Stage processing detects various errors that may cause the run to terminate. Duplicate or conflicting run control parameters in the CL script file itself or on the command line cause you to be prompted at the screen for the correct information.

Control Stage errors will be found in the Log file.

 

The Pre-processor contains its own error monitoring system, which is described in the chapter on the Pre-processor.

Pre-processor errors will be found in the Log file.

 

The compiler detects three classes of error - warnings, faults, aborts and program errors. Each error message has its own identifier, beginning with one of the letters W, F, A, or P, and a text.

Compilation errors are found by searching for >> in the Listing file.

 

The execution module detects errors of various kinds in the source data, in your terminal commands and program errors.

Execution errors are found in the Report file, serious errors will be reported in the Log file.

 

The print module detects errors in laying out the tables for printing, and program errors.

Print errors will be found in the Log file.

 

In general, if an error occurs that is not self-explanatory, it is likely to be one of the following:

You have run out of hard disk storage.

Your computer is not functioning properly. Try running other software.

Your copy of CL or one of the work files used by the run has become corrupted. It is safe to reinstall CL at any time, this will not affect any project files.

You have insufficient available RAM to run CL.

You have found a problem with the program. Please let NetMR Scotland Ltd know if you think you have found a fault with CL.

In any event, you should repeat the run once (and all runs creating work files used in the run), and if the error recurs, get in touch with your distributor. Usually you will be asked to send copies of the relevant files (including a Log) to your distributor so that the problem can be checked out.