WI115: Error opening batch file for writing. There is not enough memory to create the internal structure required to write an Import specification file (an IMP file).
Close any unnecessary applications, then retry the operation. If this does not resolve the problem, clear memory by restarting
SQLWizard or by rebooting.
WI116: Error writing to batch file. An error has occurred while writing an Import specification file (an IMP file). Check that nothing is preventing a file from
being written. For example, check that the drive is operational and that it has sufficient space. Also check that the file
is not write protected.
WI117: Invalid value value for SRC_ASCII_CODEPAGE command in group Tnumber, Tname. The value assigned to a SRC_ASCII_CODEPAGE statement in your Import specification file (IMP file) is incorrect. It must be
a positive integer. The error is located in the transaction represented by Tnumber (e.g., Tnumber 1 is the first transaction in the IMP file) and Tname (Tname is the bracketed string at the top of each transaction). Allowed values are listed in the SQLWizard User's Guide.
WI118: Invalid value value for DST_ASCII_CODEPAGE command in group Tnumber, Tname. The value assigned to a DST_ASCII_CODEPAGE statement in your Import specification file (IMP file) is incorrect. It must be
a positive integer. The error is located in the transaction represented by Tnumber (e.g., Tnumber 1 is the first transaction in the IMP file) and Tname (Tname is the bracketed string at the top of each transaction). Allowed values are listed in the SQLWizard User's Guide.
WI119: Invalid batch file name filename. An invalid file name has been given to an Import specification file (IMP file). If you are saving an IMP file, check that
you have typed a name allowed by your operating system. If you are running a batch import from the command line, verify that
a valid IMP filename was entered on the command line. See your SQLWizard User's Guide for command line syntax.
WI121: Can't import data file filename into table tablename because data file has number columns but table has number columns. The source file and the target table in your Import operation do not have the same number of fields. If you are running a
batch import, verify that the TABLE statement in the IMP file is set to the correct target table. Also verify that the FIELDS,
TYPES, NULL_PERM, SRC_LENS, OFFSETS, USE_PIC and EBCDIC_TO_ASCII statements in your IMP file reflect the actual number of
columns in your source and destination. See your SQLWizard User's Guide for a complete description of the IMP file and its contents.
WI122: Batch specification in group Tnumber, Tname in file filename is not sufficient to create new table tablename. A TYPES and/or FIELDS statement for this transaction was not found in the Import specification file (IMP file). The error
is located in the transaction represented by Tnumber (e.g., Tnumber 1 is the first transaction in the IMP file) and Tname (Tname is the bracketed string at the top of each transaction). Edit your IMP file and enter the missing statement(s). See your
SQLWizard User's Guide for a complete description of the IMP file and its contents.
WI123: Table tablename contains number columns but batch file specifies number columns. The target table specified in the Import specification file (IMP file) doesn't contain the same number of fields as the source
file. Verify that the TABLE statement in the IMP file is set to the correct target table. Also verify that the FIELDS, TYPES,
NULL_PERM, SRC_LENS, OFFSETS, USE_PIC and EBCDIC_TO_ASCII statements in your IMP file reflect the actual number of columns
in your source and destination. See your SQLWizard User's Guide for a complete description of the IMP file and its contents.