| SQL3001C | An I/O error (reason = "<reason>") occurred while opening the output file. |
Explanation: A system I/O error occurred while opening the output file.
The command cannot be processed. No data is processed.
User Response: 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.
| SQL3002C | An I/O error occurred while writing to the output data file. |
Explanation: 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.
User Response: If the output data file is incomplete, erase it and resubmit the command.
| SQL3003C | An I/O error occurred while closing the output data file. |
Explanation: A system I/O error occurred while closing the output data file.
The file is not closed.
User Response: If the output data file is incomplete, erase it and resubmit the command.
| SQL3004N | The filetype parameter is not valid. |
Explanation: 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.
User Response: Resubmit the command with a valid filetype parameter.
| SQL3005N | Processing was interrupted. |
Explanation: 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.
User Response: 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.
| SQL3006C | An I/O error occurred while opening the message file. |
Explanation: 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.
User Response: Resubmit the command with a valid message file name, including the correct path.
| SQL3007C | An I/O error occurred while writing to the message file. |
Explanation: A system I/O error occurred while writing to the message file.
Processing may not have finished.
User Response: If the message file is incomplete, erase it and resubmit the command.
| SQL3008N | The utility encountered an error "<error>" while connecting to the database. |
Explanation: The IMPORT or EXPORT utility could not connect to the database.
No data is imported or exported.
User Response: Look at the error number in the message for more information. Make changes and resubmit the command.
| SQL3009N | The Action String parameter is not valid. |
Explanation: 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.
User Response: Verify the Action String pointer and the structure it points to. Resubmit the command with a valid Action String.
| SQL3010N | The METHOD parameter is not valid. |
Explanation: 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.
User Response: Examine the METHOD pointer and the structure it points to. Resubmit this command with a valid METHOD.
| SQL3011C | There is not enough storage to process the command. |
Explanation: 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.
User Response: Stop the application. Possible solutions include:
| SQL3012C | A system error occurred. |
Explanation: An operating system error occurred.
The command cannot be processed.
User Response: Check your message file, correct the problem and resubmit the command.
| SQL3013N | The length of the filetmod is out of the acceptable range. It should be greater than or equal to zero and less than or equal to 8000. |
Explanation: 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.
User Response: Examine the filetmod pointer and the structure it points to. Resubmit the command with a valid filetmod.
| SQL3014C | An I/O error occurred while closing the message file. |
Explanation: A system I/O error occurred while closing the message file.
The message file is not closed.
User Response: If the message file is incomplete, resubmit the command.
| SQL3015N | An SQL error "<sqlcode>" occurred during processing. |
Explanation: An SQL error occurred during the utility call.
The utility stops processing.
User Response: Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.
| SQL3016N | An unexpected keyword "<keyword>" was found in the filetmod parameter for the filetype. |
Explanation: 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.
User Response: 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.
| SQL3017N | A delimiter is not valid or is used more than once. |
Explanation: For Delimited ASCII (DEL) files, one of two errors occurred:
The command cannot be processed.
User Response: Examine the specified delimiters for validity and uniqueness. Resubmit the command with valid delimiter overrides.
| SQL3018N | The period was specified as a character string delimiter. |
Explanation: For Delimited ASCII (DEL), the period cannot be specified as the character string delimiter.
The command cannot be processed.
User Response: Resubmit the command with valid delimiter overrides.
| SQL3019N | No Action String parameter was specified in the command. |
Explanation: No Action String (e.g. "REPLACE into ...") parameter is specified for this utility call. This parameter is required.
The command cannot be processed.
User Response: Resubmit the command with an Action String parameter.
| SQL3020N | The user does not have the authority to run the specified Export command. |
Explanation: 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.
User Response: Request appropriate authorization before exporting data from the tables.
| SQL3021N | The user does not have the authority to run the specified Import command on table "<name>". |
Explanation: 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.
User Response: Ensure that the user has the authorization to perform the import operation.
| SQL3022N | An SQL error "<sqlcode>" occurred while processing the SELECT string in the Action String parameter. |
Explanation: 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.
User Response: Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.
| SQL3023N | The database name parameter is not valid. |
Explanation: 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.
User Response: Resubmit the statement with a valid database name parameter.
| SQL3025N | A parameter specifying a filename or path is not valid. |
Explanation: 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.
User Response: Resubmit the statement with a valid parameter.
| SQL3026N | The msgfile or tempfiles path parameter is not valid. |
Explanation: 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 tempfiles path 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.
User Response: Resubmit the statement with a valid msgfile and/or tempfiles path parameter.
| SQL3028N | The export method indicator is not valid. It must be either 'N' or 'D'. |
Explanation: The export method indicator must be either N for Names or D for Default.
The command cannot be processed.
User Response: Resubmit the statement with a valid method indicator.
| SQL3029N | No filetype parameter was specified. |
Explanation: 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.
User Response: Resubmit the statement with a valid filetype.
| SQL3030C | An I/O error (reason = "<reason>") occurred while opening the input file. |
Explanation: 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.
User Response: 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.
| SQL3031C | An I/O error occurred while reading from the input file. |
Explanation: 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.
User Response: Verify that the input file is readable.
| SQL3032N | The LOAD/IMPORT method indicator is not valid for the specified filetype. It must be either 'N', 'P', or 'default'. |
Explanation: 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.
User Response: Resubmit the command with a valid method indicator.
| SQL3033N | A keyword such as INSERT, REPLACE, CREATE, INSERT_UPDATE, or REPLACE_CREATE is missing from the target specification or it is misspelled. |
Explanation: 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.
User Response: Resubmit the command with a valid Action String parameter.
| SQL3034N | The keyword INTO is missing from the target specification or it is misspelled. |
Explanation: The INTO keyword is missing or spelled incorrectly. INTO must be followed by at least one blank.
The command cannot be processed.
User Response: Resubmit the command with a valid Action String (e.g. "REPLACE into ...") parameter.
| SQL3035N | The tablename parameter in the target specification is not valid. |
Explanation: 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.
User Response: Resubmit the command with a valid tablename. Also ensure that all command keywords and parameters are entered in the correct order.
| SQL3036N | The tcolumn-list in the target specification does not have a closed parenthesis. |
Explanation: The tcolumn-list must be delimited by parentheses. The list was not terminated by the closed parenthesis.
The command cannot be processed.
User Response: Resubmit the statement with a valid, complete column list in the Action String (e.g. "REPLACE into ...") parameter.
| SQL3037N | An SQL error "<sqlcode>" occurred during Import processing. |
Explanation: An SQL error occurred during processing of the Action String (e.g. "REPLACE into ...") parameter.
The command cannot be processed.
User Response: Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.
| SQL3038N | The Action String parameter contains unexpected characters. |
Explanation: 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.
User Response: Resubmit the command with a valid Action String parameter.
| SQL3039W | The memory available to LOAD for DATA BUFFER prohibits full LOAD parallelism. Load parallelism of "<value>" will be used. |
Explanation: 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, one of the following limitation was encountered:
A lesser degree of parallelism, requiring less memory, will be used.
User Response:
| SQL3040N | Unable to use the lobpath/lobfile parameters as specified. Reason code: "<reason-code>". |
Explanation: 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.
User Response: Given for each reason code:
| SQL3042N | The LINKTYPE specified for a DATALINK column is invalid. |
Explanation: The value specified for LINKTYPE for a DATALINK column is invalid.
User Response: Check the LINKTYPE specified. Correct the value and resubmit the command.
| SQL3043N | The DATALINK SPECIFICATION for DATALINK column(s) is invalid. |
Explanation: The DATALINK SPECIFICATION for DATALINK column(s) is invalid for one of the following reasons:
User Response: Correct the specification and resubmit the command.
| SQL3044N | The DATALINK SPECIFICATION for a DATALINK column has duplicate prefix specification. |
Explanation: The DATALINK SPECIFICATION for a DATALINK column has duplicate specifications for DL_URL_REPLACE_PREFIX or DL_URL_DEFAULT_PREFIX.
User Response: Remove the duplicate specification and resubmit the command.
| SQL3045N | A dcolumn position in the METHOD parameter is less than one or greater than the maximum number of columns (1024) in a Delimited ASCII file. |
Explanation: 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.
User Response: Resubmit the command with valid dcolumn positions.
| SQL3046N | The number of columns in the METHOD parameter is less than one. |
Explanation: For METHOD methods other than Default, the number of columns specified must be a positive number (greater than 0).
The command cannot be processed.
User Response: Resubmit the command with a valid number of columns in the METHOD parameter.
| SQL3047N | The LOAD/IMPORT method specified in METHOD is not valid for Delimited ASCII files. It must be either 'P' or 'default'. |
Explanation: The only valid LOAD/IMPORT methods for Delimited ASCII files are P for Positions or D for Default.
The command cannot be processed.
User Response: Resubmit the command with a valid import method.
| SQL3048N | There are fewer columns specified from the input file than database columns, but one of the database columns is not nullable. |
Explanation: 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.
User Response: Define a new table that has the same number of columns as the input file or that has nullable columns. Resubmit the command.
| SQL3049N | The data type "<type>" of the database column "<name>" is not compatible with this format file, but the database column is not nullable. |
Explanation: 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.
User Response: Redefine the database table so the columns are compatible with the columns loaded from the file.
| SQL3050W | Conversions on the data will be made between the IXF file code page and the application code page. |
Explanation: 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.
User Response: If you do not want a conversion to be performed, invoke the utility using the FORCEIN option; otherwise no action is required.
| SQL3051W | The data to be loaded into "<column_name>" has been loaded, but conversion from the IXF file code page to the application code page has not been performed. |
Explanation: 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.
User Response: This is a warning only.
| SQL3053N | There are more than 8191 rows to be exported to a worksheet formatted file. |
Explanation: 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.
User Response: To prevent this error, use a SELECT statement that results in fewer rows to export, and resubmit the command.
| SQL3054N | The input file is not a valid PC/IXF file. The file is too short to contain a valid H record. |
Explanation: 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.
User Response: Verify that the input file is correct.
| SQL3055N | The input file is not a valid PC/IXF file. The length field in the first record cannot be converted to a numeric value. |
Explanation: 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.
User Response: Verify that the input file is correct.
| SQL3056N | The input file is not a valid PC/IXF file. The value in the length field of the H record is too small. |
Explanation: 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.
User Response: Verify that the input file is correct.
| SQL3057N | The input file is not a valid PC/IXF file. The type field in the first record is not H. |
Explanation: 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.
User Response: Verify that the input file is correct.
| SQL3058N | The identifier field in the H record is not IXF. |
Explanation: 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.
User Response: Examine the identifier field in the H record.
| SQL3059N | The version field in the H record is not valid. |
Explanation: The version field in the H record contains a value that is not valid.
The utility stops processing. No data is loaded.
User Response: Examine the version field in the H record.
| SQL3060N | The HCNT field in the H record cannot be converted to a numeric value or the value is out of range. |
Explanation: 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.
User Response: Examine the HCNT field in the H record.
| SQL3061N | The single-byte and/or double-byte code page field in the H record cannot be converted to a numeric value or the value is out of range. |
Explanation: 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.
User Response: Examine the single-byte and double-byte code page field in the H record, change them to appropriate values as specified in the Application Development Guide and resubmit the command.
| SQL3062N | The double-byte code page field in the H record cannot be converted to a numeric value or the value is out of range. |
Explanation: 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.
User Response: Examine the double-byte code page field in the H record, change it to an appropriate value as specified in the Application Development Guide and resubmit the command.
| SQL3063N | The single-byte code page value "<value 1>" in the H record is not compatible with the single-byte code page value "<value 2>" for the application. The FORCEIN option was not specified. |
Explanation: 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.
User Response: To load this data, resubmit the command with the FORCEIN option.
| SQL3064N | The double-byte code page value "<value 1>" in the H record is not compatible with the double-byte code page value "<value 2>" for the application. The FORCEIN option was not specified. |
Explanation: 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.
User Response: To load data where the double-byte code page values do not match, resubmit the command with the FORCEIN option.
| SQL3065C | The value for the application code page cannot be determined. |
Explanation: The system encountered an error while determining the code page of the application.
The utility stops processing. No data is loaded or unloaded.
User Response: Contact your technical service representative.
| SQL3066N | While reading or looking for the T record, the end of the file was reached. |
Explanation: 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.
User Response: 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.
| SQL3067N | The length field in the T record cannot be converted to a numeric value. |
Explanation: The length field in the T record is not an ASCII representation of a number.
The utility stops processing. No data is loaded.
User Response: Examine the length field in the T record.
| SQL3068N | The value in the length field of the T record is too small. |
Explanation: 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.
User Response: Examine the length field in the T record.
| SQL3069N | The first non-A record following the H record is not a T record. |
Explanation: 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.
User Response: Examine the records following the H record.
| SQL3070N | The length field in an A record is out of range. |
Explanation: 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.
User Response: Examine the length field in the A records.
| SQL3071N | The data-convention field in the T record is not C. |
Explanation: The data-convention field in the T record is a value other than C.
The utility stops processing. No data is loaded.
User Response: Examine the data-convention field in the T record.
| SQL3072N | The data-format field in the T record is not M. |
Explanation: The data-format field in the T record is a value other than M.
The utility stops processing. No data is loaded.
User Response: Examine the data-format field in the T record.
| SQL3073N | The machine format field in the T record is not PCbbb (where b = blank). |
Explanation: The machine format 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.
User Response: Examine the machine format field in the T record.
| SQL3074N | The data-location field in the T record is not I. |
Explanation: The data-location field in the T record is a value other than I.
The utility stops processing. No data is loaded.
User Response: Examine the data-location field in the T record.
| SQL3075N | The CCNT in the T record cannot be converted to a numeric value or the value is out of range. |
Explanation: 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.
User Response: Examine the CCNT field in the T record.
| SQL3076N | The name length field in the T record cannot be converted to a numeric value or the value is out of range. |
Explanation: 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.
User Response: Examine the name length field in the T record.
| SQL3077N | The number of C records specified in the CCNT field in the T record "<value>" exceeds the maximum allowed "<maximum>". |
Explanation: 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.
User Response: Examine the CCNT field in the T record.
| SQL3078N | The length field in an A record cannot be converted to a numeric value. |
Explanation: The length field in an A record is not an ASCII representation of a number.
The utility stops processing. No data is loaded.
User Response: Examine the length fields in the A records.
| SQL3079N | The length field in a C record cannot be converted to a numeric value. |
Explanation: The length field in a C record is not an ASCII representation of a number.
The utility stops processing. No data is loaded.
User Response: Examine the length field in the C records.
| SQL3080N | The value in the length field of the C record is too small. |
Explanation: 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.
User Response: Examine the length field in the C records.
| SQL3081N | Not enough C records were found. |
Explanation: 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.
User Response: Examine the T and C records.
| SQL3082N | While reading or looking for a C record, the end of the file was reached. |
Explanation: 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.
User Response: 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.
| SQL3083N | The D-record-id field in the C record for column "<name>" cannot be converted to a numeric value. |
Explanation: 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.
User Response: Examine the D-record-id field in the C record.
| SQL3084N | The D-record-position field in the C record for column "<name>" cannot be converted to a numeric value. |
Explanation: 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.
User Response: Examine the D-record-position field in the C record.
| SQL3085N | The D-record-id and D-record-position fields in the C record for column "<name>" are out of range or inconsistent with the previous C record. |
Explanation: 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.
User Response: Examine the D-record-id and D-record-position fields in the C record.
| SQL3086N | There was no source column specified to be loaded into database column "<name>" or the specified source column does not exist, but the database column is not nullable. |
Explanation: 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.
User Response: 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.
| SQL3087N | The source column specified to be loaded into database column "<name>" is not valid, but the database column is not nullable. |
Explanation: 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.
User Response: Read the previous messages to understand why the column is not valid.
| SQL3088N | The source column specified to be loaded into database column "<name>" is not compatible with the database column, but the database column is not nullable. |
Explanation: 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.
User Response: Compare the columns in the source PC/IXF file with the columns in the database.
| SQL3089N | A non-D record was found where a D record was expected. |
Explanation: Some record other than a D record was found where a D record was expected.
The utility stops processing. No data is loaded.
User Response: Examine the D records in the file.
| SQL3090N | The length field in a D record cannot be converted to a numeric value. |
Explanation: The length field in a D record is not an ASCII representation of a number.
The utility stops processing. No data is loaded.
User Response: Examine the length field in the D records.
| SQL3091N | The length field in a D record is out of range. |
Explanation: 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.
User Response: Examine the length field in the D records.
| SQL3092N | The identifier field in a D record does not contain the expected value. |
Explanation: 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.
User Response: Examine the identifier field in the D records.
| SQL3093N | The input file is not a valid WSF file. |
Explanation: 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.
User Response: Verify that the file is a valid WSF file and that the name was entered correctly.
| SQL3094N | The input column "<name>" was not found, but the corresponding database column is not nullable. |
Explanation: 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
User Response: Verify that the input file contains the specified column names.
| SQL3095N | The specified column position "<position>" is not in the valid range of 1 to 256. |
Explanation: 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.
User Response: Verify that the specified column position is within the range 1 to 256.
| SQL3096N | The data type "<type>" of the database column "<name>" is not compatible with any WSF column type, but the database column is not nullable. |
Explanation: 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.
User Response: Redefine the database table so the columns are compatible with the columns being imported from the WSF file. Resubmit the command.
| SQL3097N | The record length field in the WSF record is not valid for its record type. |
Explanation: 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.
User Response: Regenerate the WSF file with a supported level of the Lotus product.
| SQL3098N | The row number from the input file is not in the valid range of 1 to 8192. |
Explanation: 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.
User Response: Regenerate the WSF file with a supported level of the Lotus product.
| SQL3099N | The column number from the input file is not in the valid range of 1 to 256. |
Explanation: 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.
User Response: Regenerate the WSF file with a supported level of the Lotus product.