FUNL0056 Unknown field in record (recno) ((hexDiag)).: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Created page with "A record was found containing an unknown field code. This could be the result of running with the NOENQ parameter against a database file that has just had a fieldname or fieldna...")
 
(Automatically generated page update)
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
A record was found containing an unknown field code. This could be the result of running with the NOENQ parameter against a database file that has just had a fieldname or fieldnames added or of running against an unenqueued found set or list when using the ''[[Fast/Unload User Language Interface]]''. This can also be an indication of an integrity problem in your database file. You can change the action to be taken when this situation is encountered by setting the HARDERR parameter. The default action is to cancel the run.  
A record was found containing an unknown field code. This could be the result of running with the NOENQ parameter against a database file that has just had a fieldname or fieldnames added or of running against an unenqueued found set or list when using the [[Fast/Unload User Language Interface]]. This can also be an indication of an integrity problem in your database file. You can change the action to be taken when this situation is encountered by setting the HARDERR parameter. The default action is to cancel the run.  


Starting with version 4.4 of ''[[Fast/Unload]]'', the end of this message shows a hexadecimal diagnostic code which may be useful if Sirius Software support needs to diagnose the situation.
The end of this message shows a hexadecimal diagnostic code which may be useful if Rocket Software technical support needs to diagnose the situation.


[[Category:Fast/Unload Messages]]
[[Category:Fast/Unload messages]]

Latest revision as of 13:41, 19 April 2013

A record was found containing an unknown field code. This could be the result of running with the NOENQ parameter against a database file that has just had a fieldname or fieldnames added or of running against an unenqueued found set or list when using the Fast/Unload User Language Interface. This can also be an indication of an integrity problem in your database file. You can change the action to be taken when this situation is encountered by setting the HARDERR parameter. The default action is to cancel the run.

The end of this message shows a hexadecimal diagnostic code which may be useful if Rocket Software technical support needs to diagnose the situation.