Cause: A system I/O error occurred while opening the output file.
The command cannot be processed. No data is processed.
Action: For IMPORT/LOAD, verify that the output file exists. For EXPORT, verify that the output media has enough free space. Resubmit the command with a valid output file name, including the correct path. Look in the message file for additional information.
Cause: A system I/O error occurred while writing to the output data file. The output may be incomplete or the disk may be full.
The utility stops processing.
Action: If the output data file is incomplete, erase it and resubmit the command.
Cause: A system I/O error occurred while closing the output data file.
The file is not closed.
Action: If the output data file is incomplete, erase it and resubmit the command.
Cause: The filetype parameter must be DEL, ASC, IXF, WSF, or DB2CS for the command.
The filetype parameter must be DEL, IXF, or WSF for the EXPORT command.
The filetype parameter must be ASC, DEL, IXF, or DB2CS for the LOAD command.
IXF files can not be used to load into a table defined on a multinode nodegroup.
The command cannot be processed.
Action: Resubmit the command with a valid filetype parameter.
Cause: An interrupt was received during processing. The user may have pressed the interrupt key sequence.
The utility stops processing. Any database updates not committed are rolled back.
Action: Resubmit the command. If doing an import, see Command Reference for information on how to use commitcount and restartcount parameters. If doing a load, see Command Reference for information on how to restart the load.
Cause: A system I/O error occurred while opening the message file. This error can refer to a problem on either the client or the server.
The command cannot be processed.
Action: Resubmit the command with a valid message file name, including the correct path.
Cause: A system I/O error occurred while writing to the message file.
Processing may not have finished.
Action: If the message file is incomplete, erase it and resubmit the command.
Cause: The IMPORT or EXPORT utility could not connect to the database.
No data is imported or exported.
Action: Look at the error number in the message for more information. Make changes and resubmit the command.
Cause: The Action String (e.g. "REPLACE into ...") parameter in the command is not valid. The Action String pointer may be incorrect. The structure that the Action String points to may be incorrect. The Action String structure may contain characters that are not valid.
The command cannot be processed.
Action: Verify the Action String pointer and the structure it points to. Resubmit the command with a valid Action String.
Cause: The METHOD parameter in the command is not valid. The METHOD pointer may be incorrect. The structure that the METHOD points to may be incorrect. The METHOD structure may contain characters that are not valid.
The command cannot be processed.
Action: Examine the METHOD pointer and the structure it points to. Resubmit this command with a valid METHOD.
Cause: A memory allocation error occurred. Not enough memory is available to process the command, or there was an error freeing storage.
The command cannot be processed.
Action: Stop the application. Possible solutions include:
Cause: An operating system error occurred.
The command cannot be processed.
Action: Check your message file, correct the problem and resubmit the command.
Cause: The filetmod specified is outside the acceptable range (greater than or equal to zero and less than or equal to 8000).
The command cannot be processed.
Action: Examine the filetmod pointer and the structure it points to. Resubmit the command with a valid filetmod.
Cause: A system I/O error occurred while closing the message file.
The message file is not closed.
Action: If the message file is incomplete, resubmit the command.
Cause: An SQL error occurred during the utility call.
The utility stops processing.
Action: Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.
Cause: A keyword that does not apply to the filetype for the utility was found in the filetype modifier (the filetmod parameter or the phrase following MODIFIED BY in a CLP command).
The utility stops processing.
Action: Remove the filetype modifier or specify at least one valid keyword in the filetype modifier. See the Command Reference for more information on filetype modifiers.
Cause: For Delimited ASCII (DEL) files, one of two errors occurred:
The command cannot be processed.
Action: Examine the specified delimiters for validity and uniqueness. Resubmit the command with valid delimiter overrides.
Cause: For Delimited ASCII (DEL), the period cannot be specified as the character string delimiter.
The command cannot be processed.
Action: Resubmit the command with valid delimiter overrides.
Cause: No Action String (e.g. "REPLACE into ...") parameter is specified for this utility call. This parameter is required.
The command cannot be processed.
Action: Resubmit the command with an Action String parameter.
Cause: The user attempted to export data without the appropriate authorization (either the SYSADM or DBADM authority), or the CONTROL or SELECT privilege for each table involved in the export.
The export action is not performed.
Action: Request appropriate authorization before exporting data from the tables.
Cause: The user attempted to import data without the appropriate authorization for the specified option and table.
Import using the INSERT option requires one of the following:
Note: entire hierarchy refers to all subtables or object views in the hierarchy.
Import to an existing table or view using the INSERT_UPDATE, REPLACE, or the REPLACE_CREATE option, requires one of the following:
Note: entire hierarchy refers to all subtables or object views in the hierarchy.
Import to a table that does not exist, using the CREATE or REPLACE_CREATE option, requires one of the following:
The import operation is not performed.
Action: Ensure that the user has the authorization to perform the import operation.
Cause: In IMPORT or EXPORT, during processing of the SELECT string from the Action String (e.g. "REPLACE into ...") structure, an SQL error occurred.
The command cannot be processed.
Action: Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.
Cause: The database name parameter is not valid. See the SQLERRD[0] field in the SQLCA for more information.
The database name must contain 1 to 8 characters and the characters must be from the database manager base character set.
The command cannot be processed.
Action: Resubmit the statement with a valid database name parameter.
Cause: The parameter contains a path, directory, or file name that is not valid.
For IMPORT and EXPORT, verify the datafile parameter.
For LOAD, verify that each entry in the parameters of type sqlu_media_list: datafile should contain valid filenames; lobpaths copytarget, and workdirectory should contain valid paths on the server including the final separator and a null terminator.
The pointer to lobpaths, copytarget and workdirectory must be valid or null.
The pointer to the targets in these structures must be valid.
Check that sessions and media_type are specified correctly.
Also, if the lobpaths parameter is specified, check that the media_type is the same as that specified for the datafile structure.
If the filetype is IXF, the length of the file name may be too long.
The command cannot be processed.
Action: Resubmit the statement with a valid parameter.
Cause: For IMPORT or EXPORT, the msgfile parameter contains a path, directory, or file name that is not valid.
For LOAD, either the msgfile parameter contains a path, directory, or file name that is not valid on the client, or the remotefile parameter contains a path, directory, or file name that is not valid on the server.
If the database to which the application is connected is a remote database, the msgfile must be fully qualified. For a local database the utility will attempt to fully qualify the msgfile if it is not already fully qualified. Also verify that the pointer to the msgfile is valid.
The command cannot be processed.
Action: Resubmit the statement with a valid msgfile and/or remotefile parameter.
Cause: The export method indicator must be either N for Names or D for Default.
The command cannot be processed.
Action: Resubmit the statement with a valid method indicator.
Cause: The filetype parameter was either not specified or null. The system does not know which format to use for the data file.
The command cannot be processed.
Action: Resubmit the statement with a valid filetype.
Cause: A system I/O error occurred while opening the input file. This error can refer to a problem on either the client or the server.
A possible cause may be that the input file is in use by another application.
The command cannot be processed.
Action: Ensure that the input file is valid, including the path, and that it is not currently in use by another application.
Resubmit the command. Look in the diagnostics log file for additional information.
Cause: A system I/O error occurred while reading from the input file. This error can refer to a problem on either the client or the server.
The command cannot be processed.
Action: Verify that the input file is readable.
Cause: For the IXF and WSF filetypes, the LOAD/IMPORT method indicator must be either N for Names, P for Positional, or D for Default.
The command cannot be processed.
Action: Resubmit the command with a valid method indicator.
Cause: For IMPORT, the Action String (e.g. "REPLACE into ...") parameter does not contain the keyword INSERT, REPLACE, CREATE, INSERT_UPDATE, or REPLACE_CREATE. For LOAD, the Action String parameter does not contain the keyword INSERT, REPLACE, or RESTART. The keyword must be followed by at least one blank.
The command cannot be processed.
Action: Resubmit the command with a valid Action String parameter.
Cause: The INTO keyword is missing or spelled incorrectly. INTO must be followed by at least one blank.
The command cannot be processed.
Action: Resubmit the command with a valid Action String (e.g. "REPLACE into ...") parameter.
Cause: For IMPORT, the tablename in the Action String (e.g. "REPLACE into ...") is not valid. For LOAD, the tablename or the exception tablename in the Action String is not valid.
The command cannot be processed.
Action: Resubmit the command with a valid tablename. Also ensure that all command keywords and parameters are entered in the correct order.
Cause: The tcolumn-list must be delimited by parentheses. The list was not terminated by the closed parenthesis.
The command cannot be processed.
Action: Resubmit the statement with a valid, complete column list in the Action String (e.g. "REPLACE into ...") parameter.
Cause: An SQL error occurred during processing of the Action String (e.g. "REPLACE into ...") parameter.
The command cannot be processed.
Action: Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.
Cause: For IMPORT, there are characters other than blanks after the closing parenthesis of the column list in the Action String (e.g. "REPLACE into ...") parameter. For LOAD, there are characters other than blanks after the closing parenthesis of the column list and/or the exception tablename in the Action String parameter.
The command cannot be processed.
Action: Resubmit the command with a valid Action String parameter.
Cause: The LOAD utility attempted to determine the optimal level of CPU parallelism for SMP exploitation based on the system configuration, or the user specified a value for LOAD parallelism when invoking the utility. However, the amount of free memory in the utility heap prohibits this degree of parallelism. A lesser degree of parallelism, suitable for the memory available, will be used.
Action:
Cause: The utility is unable to use the lobpath or lobfile parameters as specified for the reason given by "<reason-code>". The codes are listed below.
Action: Given for each reason code:
Cause: The dcolumn position is less than 1 or greater than the maximum number of columns (1024) in a delimited file.
The command cannot be processed.
Action: Resubmit the command with valid dcolumn positions.
Cause: For METHOD methods other than Default, the number of columns specified must be a positive number (greater than 0).
The command cannot be processed.
Action: Resubmit the command with a valid number of columns in the METHOD parameter.
Cause: The only valid LOAD/IMPORT methods for Delimited ASCII files are P for Positions or D for Default.
The command cannot be processed.
Action: Resubmit the command with a valid import method.
Cause: When fewer columns are specified in the METHOD list than are specified for the target table, the values for the missing input columns are loaded as nulls. Because the columns in the target table that correspond to one or more of these input columns are not nullable, null cannot be inserted.
The file cannot be loaded.
Action: Define a new table that has the same number of columns as the input file or that has nullable columns. Resubmit the command.
Cause: The database column type is not valid for this format file. The database column is not nullable so the utility is ended.
The utility stops processing. No data is loaded.
Action: Redefine the database table so the columns are compatible with the columns loaded from the file.
Cause: If an IMPORT of an IXF data file has been issued and the code page of the character data in the IXF file is different from the code page of the application invoking the import operation, a conversion will be made from the code page of the data file to the code page of the application and the operation will continue.
If a LOAD of an IXF data file has been issued and the code page of the character data in the IXF file is different from the database code page, a conversion will be made from the code page of the data file to the code page of the database and the operation will continue.
Action: If you do not want a conversion to be performed, invoke the utility using the FORCEIN option; otherwise no action is required.
Cause: The data that was loaded into the CLOB or DBCLOB column is stored in a separate file and no conversions have been performed on it.
To properly load the data, call the utility from an application that has the same code page as the IXF file.
Action: This is a warning only.
Cause: The maximum number of rows that can be placed in a worksheet format file (WSF) is 8191.
The EXPORT utility stops processing after placing 8191 rows in the file.
Action: To prevent this error, use a SELECT statement that results in fewer rows to export, and resubmit the command.
Cause: The end of the file was reached before the expected end of the first record. The file may not be a PC/IXF file.
The LOAD/IMPORT utility stops processing. No data is imported.
Action: Verify that the input file is correct.
Cause: The value in the length field of the first record is not the ASCII representation of a number. The file may not be a PC/IXF file.
The utility stops processing. No data is loaded.
Action: Verify that the input file is correct.
Cause: The value in the length field of the H record is not large enough for a valid H record. The file may not be a PC/IXF file.
The utility stops processing. No data is loaded.
Action: Verify that the input file is correct.
Cause: The type field in the first record is not H. The first record is not a valid H record. The file may not be a PC/IXF file.
The utility stops processing. No data is loaded.
Action: Verify that the input file is correct.
Cause: The identifier field in the H record does not identify the file as a PC/IXF file.
The utility stops processing. No data is loaded.
Action: Examine the identifier field in the H record.
Cause: The version field in the H record contains a value that is not valid.
The utility stops processing. No data is loaded.
Action: Examine the version field in the H record.
Cause: The Heading-record-count field in the H record is not an ASCII representation of a number or is a number that is not valid for this field.
The utility stops processing. No data is loaded.
Action: Examine the HCNT field in the H record.
Cause: The single-byte and/or double-byte code page field in the H record is not an ASCII representation of a number or is a number that is not valid for this field.
The utility stops processing. No data is loaded.
Action: Examine the single-byte and double-byte code page field in the H record, change them to appropriate values as specified in the API Reference and resubmit the command.
Cause: The double-byte code page field in the H record is not an ASCII representation of a number or is a number that is not valid for this field.
The utility stops processing. No data is loaded.
Action: Examine the double-byte code page field in the H record, change it to an appropriate value as specified in the API Reference and resubmit the command.
Cause: The single-byte code page value in the H record is not compatible with the application code page value. When the FORCEIN option is not used, the data cannot be loaded unless conversion from value 1 to value 2 is supported.
The utility stops processing. No data is loaded.
Action: To load this data, resubmit the command with the FORCEIN option.
Cause: The double-byte code page value in the H record is not compatible with the application code page value. When the FORCEIN option is not used, the data cannot be loaded unless value 1 and value 2 are the same.
The utility stops processing. No data is loaded.
Action: To load data where the double-byte code page values do not match, resubmit the command with the FORCEIN option.
Cause: The system encountered an error while determining the code page of the application.
The utility stops processing. No data is loaded or unloaded.
Action: Contact your technical service representative.
Cause: The end of the file was reached while the system was looking for the T record or while it was reading the T record.
The utility stops processing. No data is loaded.
Action: Examine the T record of the input file. If the PC/IXF file was copied from one medium to another, compare the copy with the original or repeat the copy process.
Cause: The length field in the T record is not an ASCII representation of a number.
The utility stops processing. No data is loaded.
Action: Examine the length field in the T record.
Cause: The value in the length field of the T record is not large enough so the T record is not valid.
The utility stops processing. No data is loaded.
Action: Examine the length field in the T record.
Cause: After the H record, the first record not an A record is also not a T record. The H record must be immediately followed by a T record but A records may exist before the T record.
The utility stops processing. No data is loaded.
Action: Examine the records following the H record.
Cause: The length field in an A record is a number that is not valid for this field.
The utility stops processing. No data is loaded.
Action: Examine the length field in the A records.
Cause: The data-convention field in the T record is a value other than C.
The utility stops processing. No data is loaded.
Action: Examine the data-convention field in the T record.
Cause: The data-format field in the T record is a value other than M.
The utility stops processing. No data is loaded.
Action: Examine the data-format field in the T record.
Cause: The machine-form field in the T record is a value other than PCbbb, where each b is a blank.
The utility stops processing. No data is loaded.
Action: Examine the machine-form field in the T record.
Cause: The data-location field in the T record is a value other than I.
The utility stops processing. No data is loaded.
Action: Examine the data-location field in the T record.
Cause: The C-record count field in the T record is not an ASCII representation of a number or is a number that is not valid for this field.
The utility stops processing. No data is loaded.
Action: Examine the CCNT field in the T record.
Cause: The name length field in the T record is not an ASCII representation of a number or is a number that is not valid for this field.
The utility stops processing. No data is loaded.
Action: Examine the name length field in the T record.
Cause: The value in the CCNT field of the T record is larger than the maximum allowed for the indicated release.
The utility stops processing. No data is loaded.
Action: Examine the CCNT field in the T record.
Cause: The length field in an A record is not an ASCII representation of a number.
The utility stops processing. No data is loaded.
Action: Examine the length fields in the A records.
Cause: The length field in a C record is not an ASCII representation of a number.
The utility stops processing. No data is loaded.
Action: Examine the length field in the C records.
Cause: The value in the length field of a C record is not large enough so the C record is not valid.
The utility stops processing. No data is loaded.
Action: Examine the length field in the C records.
Cause: The number of C records found (in the correct position) is less than the number expected from the C-record-count (CCNT) in the T record.
The utility stops processing. No data is loaded.
Action: Examine the T and C records.
Cause: The end of the file was reached while the system was looking for a C record or while it was still reading a C record.
The utility stops processing. No data is loaded.
Action: Examine the C records in the input file. If the PC/IXF file was copied from one medium to another, compare the copy with the original or repeat the copy process.
Cause: The D-record-id field in the C record for the indicated column is not an ASCII representation of a number.
The utility stops processing. No data is loaded.
Action: Examine the D-record-id field in the C record.
Cause: The D-record-position field in the C record for the indicated column is not an ASCII representation of a number.
The utility stops processing. No data is loaded.
Action: Examine the D-record-position field in the C record.
Cause: The D-record-id or the D-record-position fields in the C record for the indicated column contain a value that is either out of the value range or is not correct relative to the previous C record.
The utility stops processing. No data is loaded.
Action: Examine the D-record-id and D-record-position fields in the C record.
Cause: Either there was not a PC/IXF column specified to be exported into the indicated column or the specified PC/IXF source column does not exist. Nulls cannot be inserted because the database column is not nullable.
The utility stops processing. No data is loaded.
Action: Check the METHOD parameter for erroneous names or positions or for fewer entries in the METHOD parameter than the Action String (e.g. "REPLACE into ...") parameter states or implies.
Cause: The PC/IXF column cannot be loaded into the indicated database column and the reason was given in a previous message in the message log. Nulls cannot be inserted because the database column is not nullable.
The utility stops processing. No data is loaded.
Action: Read the previous messages to understand why the column is not valid.
Cause: The source PC/IXF column is not compatible with the target database column. The column types or lengths may be incompatible. Nulls cannot be inserted because the database column is not nullable.
The utility stops processing. No data is loaded.
Action: Compare the columns in the source PC/IXF file with the columns in the database.
Cause: Some record other than a D record was found where a D record was expected.
The utility stops processing. No data is loaded.
Action: Examine the D records in the file.
Cause: The length field in a D record is not an ASCII representation of a number.
The utility stops processing. No data is loaded.
Action: Examine the length field in the D records.
Cause: The length field in a D record is a number that is not valid for this field.
The utility stops processing. No data is loaded.
Action: Examine the length field in the D records.
Cause: The identifier field in a D record is not valid. One or more D records may have been written out of sequence.
The utility stops processing. No data is loaded.
Action: Examine the identifier field in the D records.
Cause: The first record in the worksheet format (WSF) file was not a beginning-of-file (BOF) record, or the version of the WSF file is not supported.
The IMPORT utility stops processing. No data is imported.
Action: Verify that the file is a valid WSF file and that the name was entered correctly.
Cause: The specified column was not in the input file. Because the corresponding database column is not nullable, data cannot be loaded into the column.
The utility stops processing. No data is loaded. The column names processed before the error occurred are in the database
Action: Verify that the input file contains the specified column names.
Cause: A column position was specified that was not within the range of 1 to 256.
The utility stops processing. No data is loaded. The column names processed before the error occurred are in the database.
Action: Verify that the specified column position is within the range 1 to 256.
Cause: There is not any worksheet format (WSF) column type that is compatible with the indicated database column. The database column is not nullable so the IMPORT utility stops processing.
No data is imported.
Action: Redefine the database table so the columns are compatible with the columns being imported from the WSF file. Resubmit the command.
Cause: The worksheet format (WSF) records have an expected fixed length or a variable-length range. The record does not contain the fixed length, or the variable length is out of range. Some damage occurred to the WSF file, or it was generated incorrectly, possibly with a level of the Lotus product not supported by the database manager.
The IMPORT utility stops processing.
Action: Regenerate the WSF file with a supported level of the Lotus product.
Cause: The maximum number of rows that a worksheet format (WSF) spreadsheet can contain is 8192. The cell coordinate contains a value outside the valid range. Some damage occurred to the WSF file, or it was generated incorrectly, possibly with a level of the Lotus product not supported by the database manager.
The IMPORT utility stops processing.
Action: Regenerate the WSF file with a supported level of the Lotus product.
Cause: The maximum number of columns that a worksheet format (WSF) spreadsheet can contain is 256. The cell coordinate contains a value outside the valid range. Some damage has occurred to the WSF file, or it was generated incorrectly, possibly with a level of the Lotus product that is not supported by the database manager.
The IMPORT utility stops processing.
Action: Regenerate the WSF file with a supported level of the Lotus product.