|
|
| Line 1: |
Line 1: |
| == Introduction == | | == Introduction == |
| '''This command for CumulusUtils has been removed as from version 6.23.0'''
| | This command for CumulusUtils has been removed as from version 6.23.0 |
| | |
| == Operation ==
| |
| This command can only be given on its own: when ready CumulusUtils exits and the logfile needs to be studied. The following command is given:
| |
| utils/bin/cumulusutils.exe CheckOnly
| |
| | |
| == Output ==
| |
| This command has no output in itself (see Inner working below).
| |
| | |
| == Inifile parameters ==
| |
| The command has one parameter by itself in the General section. ''IgnoreDataErrors'' plays a role.
| |
| [General]
| |
| IgnoreDataErrors=true | false (true is default, see below)
| |
| | |
| == Inner working ==
| |
| The general parameter ''IgnoreDataErrors'' regulates if CumulusUtils stops on first error or whether it continues reading all datafiles. If you have a lot of datafiles, it may be opportune to set this variable to false in the operational situation so it does not run to completion in case it finds a data error (e.g. after a power failure).
| |
| | |
| This command has no output in itself but possible data errors are reported in the logfile.
| |
| It is then up to the user to either correct these or accept the errors as unavoidable and acceptable.
| |
| | |
| The following errors are detected:
| |
| #Overflow errors in the numbers
| |
| #Formatting errors in dates and numbers
| |
| #Old datafile formats where certain fields do not exist.
| |
| | |
| In all cases you get a message of the form (may differ slightly):
| |
| {m} fail: {e.Message}
| |
| {m}: in field nr {FieldInUse} ({FieldInUse-Name})
| |
| {m}: line is: {line}
| |
| | |
| This message gives you field name, filename and line number in the datafile where the error occurred.
| |
|
| |
|
| [[Category:CumulusUtils]] | | [[Category:CumulusUtils]] |
