You are here: Available Utilities > F > FIXOFFS > Warning and Error Messages

Warning and Error Messages

Here are descriptions of the warning and error messages you may encounter.

Command Line Parameter Already Defined

This warning message tells you a command line parameter has been entered more than once.

Command Line Parameter Does Not have Value

This warning message indicates you specified a command line parameter but omitted its value. Follow each command line parameter with an equal sign (=) and a value, as shown here:

fixofw32 -ini=fsiuser.ini (correct)

fixofw32 -ini fsiuser.ini (incorrect)

Error in Logging

This warning message indicates the utility was unable to record an entry to the log file.

Input and Output Files have the Same Path and File Name

A warning issued if the output and input files you specified in the INI file are identical. For this to occur the Print_Batches control group must be identical to the Fix_Batches control group, and the OutPath option in the FixOffsets control group must be identical to the DataPath option in the Data control group. The utility modifies the offsets of the existing file.

<FixOffsets><LogFields> Specified But Not Found in Record

This warning message indicates the LogFields option in the FixOffsets control group defined fields which are not in defined in the TRNDFDFL.DFD or RCBDFDFL.DFD files. Since this affects only the logging of messages, the utility alerts you to the situation and continues processing.

Unknown Command Line Parameter Ignored

This warning message indicates you included a command line parameter the utility did not understand and therefore ignored. Use the Help (?) parameter or refer to the syntax discussion for a list of valid command line parameters.

Not Defined in INI File

A warning or an error message is issued if the utility cannot find an option it needs in the INI file. If the message says WARNING, the next entry indicates the value the utility will use as default.

Cannot Add to Link List

This error message occurs if the utility cannot create or add to a link list.

Could Not Load INI Data

This error message that indicates either the INI file could not be opened or a required option in the INI file is missing. If a required option is missing, look in the log file for information on the option you need to add.

End of Docset Without Data

This error message indicates an end of docset marker was found in the NAFILE.DAT file or POLFILE.DAT file without any preceding data.

End of File Never Reached

This error message indicates a file has unprocessed data. All input files must be from the same run of the GenData program.

Failed to Get Record fgets

This error message tells you the utility could not read a record from the NAFILE.DAT or POLFILE.DAT files. This message is followed by additional information which tells you which file produced the error.

Failed to Return File Position ftell

This error message indicates an ftell function call returned an error. This message is followed in the log file by an entry that indicates which file produced the error and information that describes the system-level error message.

Failure to Update Record

This error message indicates the utility could not change or add a record. The following error messages indicate the utility cannot open a file it needs and generate the Failure to Update Record error message. These messages indicate why the utility could not change or add a record in a database file and are used for debugging purposes.

Could not store NAOFFSET field

Could not store POLOFFSET field

DBGotoNthRecord(%p, %p, %lu) - FAILED

DBAdd(%p,%p,%u) - FAILED

DBGetFirstRecord(%p,%p,%u) - FAILED

DBGetCurrRecNum(%p, %p) - FAILED

DBGetFieldDataPtr(%p, %p, %s) - FAILED

Could not copy data to new record

Fatal Error Cannot Continue

This error message indicates an error occurred and processing was terminated. All error messages terminate processing, but since some messages may be used as warnings or errors this message accompanies the more serious errors.

File Could Not be Opened

This error message tells you the utility could not open a file it needs for processing. The utility includes the name of the file and the file definition, if applicable, as the next entry in the log file. If you encounter this error, make sure the files indicated in the log file are present and have proper permissions.

The following error messages indicate the utility cannot open a file it needs and generate the File Could Not be Opened error message. These messages indicate why a database file was not opened and are used for debugging purposes.

Invalid Record size returned by DBAllocateStructMemory

DBAlloateStructMemory failed(%p, %p)

DBOpen(%p, %d) failed

DBInitializeFile(%s, %s, %p) failed

DBQueryFormatInfo(%s) failed

DBInitDB((FAPDBINSTALLER)ASCInstallHandler, ASCII) failed

DBPutFieldData(%p,%p,%s,%p,%u) - FAILED

File Not Sorted by X_Offset (file name)

This error message indicates the utility detected a record that was not sorted by the X_OFFSET field. The NEWTRN.DAT file and all batch files must be sorted by the X_OFFSET field.

Output File Defined in Fix_Batches Without Matching Entry in Print_Batches