1
|
End of record error, which may occur on a buffered disk write operation if the data is too long for the record buffer. This error is rare in UnForm jobs, but could occur if output is being printed to a printer alias defined in the config.unf file.
|
2
|
End of file, which may indicate a disk full message, or a file that is too large for the operating system to handle.
|
10
|
An invalid file name was given.
|
11
|
A missing key on a keyed read operation, or a duplicate key on a keyed write operation with a DOM= option.
|
12
|
A missing file error on a file open operation, or a duplicate file error on a file creation operation.
|
13
|
Normally a file permission error.
|
14
|
A file channel conflict or locking conflict error.
|
16
|
Out of resources, such as file handles. If this error occurs, it is often due to opening too many files. This can easily occur if files are opened but not closed in a loop or call construct.
|
18
|
Normally a file or directory permission error.
|
20
|
Syntax error. Common causes include mismatched parentheses, incorrect spelling of verbs or functions, or missing or incorrect function arguments.
|
21 or 25
|
Missing statement, as referenced in an ERR=label, or a goto or gosub branch.
|
23
|
Missing GBL/STBL variable name, or missing string template variable.
|
26
|
String/Number mismatch, where a string variable or literal is used where a number is expected, or visa versa.
|
27
|
Stack error, such as a return without a gosub, or a wend without a while.
|
28
|
For/Next error, such as executing a next without an associated for.
|
29
|
Mnemonic error. Mnemonics are pre-defined codes inside single quotes, such as 'FF' or 'LF'. Therefore, single quotes are not valid as string literal indicators; only double quotes are.
|
30
|
Corrupt program, which indicates that UnForm itself is probably corrupted, unless this error occurs on a call statement referencing an external program.
|
31
|
Out of memory.
|
33
|
Out of memory.
|
36
|
Mismatched arguments on a call statement.
|
40
|
Numeric overflow, normally caused by a divide by zero.
|
41
|
An integer overflow or range error. Some functions require integer arguments, so a floating point number will cause this error. Also, some functions require integer arguments to fall in a certain range, and this error will occur if the function is given a value outside of the valid range.
|
42
|
Array subscript error.
|
43
|
Masking error.
|
46
|
String length error.
|
47
|
Substring error, such as a starting position of 0 or a length greater than the length of the string.
|
119
|
When running in evaluation mode, there is a limit of 5,000 records in data files. The error occurs when trying to write too many records to a file. An evaluation version can still read records from larger files, but cannot modify them. To prevent the error, production versions of UnForm must run under a non-evaluation license.
|
996
|
The client's authkey value does not match the server's.
|
997
|
The client's IP address is not in the server's list of valid addresses. To correct this problem, the allow= line in the server's uf101d.ini file must be modified to match the network addresses in use, and the uf101d server restarted.
|
998
|
The maximum number of concurrent jobs licensed was exceeded.
|
999
|
The server was unable to start the secondary process to handle the job within the allotted time of 30 seconds. Possible causes include a sluggish server and network problems, such as a DNS server timeout.
|
1024
|
The Windows uf101c.exe client can report this error if the network connection to the server is too slow.
|
1057
|
The Windows uf101c.exe client can report this error if the server is not running or a firewall is blocking the primary listening port.
|
1058
|
If a handler process fails to start at the server upon a job connection from a client, this error is reported to the client.
|