MSIR.0229 Field causing error = (fieldname): Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
(Automatically generated page update)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This message is always preceded by an M204.1864 or an M204.1828 message, which indicates that ''[[Fast/Reload]]'' has determined it needs to do a sort of ordered index data but either the FILELOAD command was missing the VL parameter or no variable length deferred index update file was provided for the FLOD command. This problem can be caused by fields being unloaded without the ordered index (UAI OINDEX). If the original file was unloaded with UAI OINDEX then this problem can be caused if the field ''''fieldname'''' is changed from NOT ORDERED to ORDERED or ORDERED NUMERIC to ORDERED CHARACTER or vice versa. Note that the presence of this error message indicates that at least one record had a value for the field ''''fieldname'''' field.
This message is always preceded by an M204.1864 or an M204.1828 message, which indicates that [[Media:FrelrNew.pdf|Fast/Reload]] has determined it needs to do a sort of ordered index data but either the FILELOAD command was missing the VL parameter or no variable length deferred index update file was provided for the FLOD command. This problem can be caused by fields being unloaded without the ordered index (UAI OINDEX). If the original file was unloaded with UAI OINDEX then this problem can be caused if the field '''''fieldname''''' is changed from NOT ORDERED to ORDERED or ORDERED NUMERIC to ORDERED CHARACTER or vice versa. Note that the presence of this error message indicates that at least one record had a value for the field '''''fieldname''''' field.


[[Category:Sirius Mods messages]]
{{Template:MSIR.0229 footer}}
[[Category:MSIR.0200 - MSIR.0399]]

Latest revision as of 23:08, 3 March 2017

This message is always preceded by an M204.1864 or an M204.1828 message, which indicates that Fast/Reload has determined it needs to do a sort of ordered index data but either the FILELOAD command was missing the VL parameter or no variable length deferred index update file was provided for the FLOD command. This problem can be caused by fields being unloaded without the ordered index (UAI OINDEX). If the original file was unloaded with UAI OINDEX then this problem can be caused if the field fieldname is changed from NOT ORDERED to ORDERED or ORDERED NUMERIC to ORDERED CHARACTER or vice versa. Note that the presence of this error message indicates that at least one record had a value for the field fieldname field.


Message attributes:

RETCODEO=0Sets online return code
RETCODEB=0Sets batch (single user) return code
CLASS=IInformation class; the message can be suppressed with the X'02' bit setting of the MSGCTL parameter
AUDITMSWrites the message with line type MS to the audit trail
NOCOUNTDoes not increment the error count (ERCNT) parameter

Back to list of messages