End Code 43

Input file format error
%s The field number %d contains invalid data.

1:

(No message detail)

Description:

The numeric data of the input CSV data begins with a period (.).

Action to take:

Treat the input data as character data by enclosing it in enclosure characters or by adding a 0 before the period.

3:

The character string is not enclosed with the enclosure characters (0x%02X).

Description:

The enclosure character is set in the CSV data format information, but the character data of the input file or of the matching file is not enclosed in enclosure characters.

Action to take:

Check the input-side data file and the data format information.

4:

(No message detail)

Description:

A memory allocation error or an error of unknown cause occurred. The environment might be invalid, or a failure might have occurred.

Action to take:

Check the memory.

Collect data and management information, and then contact customer support.

5:

The number of fields defined in CSVID (%s) is %d, but field %d occurred.

Description:

The format of the input file or matching file is "CSV", and the number of fields defined in the CSV format differs from the number of fields in the file.

For example, if 5 fields are defined in a CSV format, this error occurs if the input side has 6 file fields.

Action to take:

Check the input-side data file and the data format information.

6:

No input data matches the field (%s).

Description:

The format of the input file or matching file is "CSV", and the number of fields defined in the CSV format differs from the number of fields in the file.

For example, if 5 fields are defined in a CSV format, this error occurs if the input side has 4 file fields.

Action to take:

Check the input-side data file and the data format information.

7:

(For sign-position errors)

Sign check error. The sign (%X) is an invalid value in field type (%c).

(For numeric-position errors)

The numeric part (the last 4 bits) contains a value that is outside the range from 0x0 to 0x9.

(For zone-sign errors)

An invalid zone code (%X) exists.

%X is set for zone code in format information.

Description:

An attempt to convert 9-type data to 9-type data failed.

For example:

  1. A value that was not specified in the zone sign of the input format was input in the zone position of the input data.

  2. A value other than a value from 0x0 to 0x9 is contained in the numeric position (the last four bits).

Action to take:

Check the input-side data file and the data format information.

8:

(For sign-position errors)

Sign check error. The sign (%X) is an invalid value in field type (%c).

(For numeric-position errors)

The numeric part contains a value that is outside the range from 0x0 to 0x9.

Description:

An attempt to convert P-type data to 9-type data failed.

For example:

  1. A value to be treated as an error in the inside sign of the input format was input in the sign position of the input data.

  2. A value other than a value from 0x0 to 0x9 is contained in the numeric position.

Action to take:

Check the input-side data file and the data format information.

9:

(For sign-position errors)

Sign check error. The sign (%X) is an invalid value in field type (%c).

(For numeric-position errors)

A value other than a value from 0x0 to 0x9 is contained in the numeric position (the last four bits).

(For zone-sign errors)

An invalid zone code (%X) exists.

%X is set for zone code in format information.

Description:

An attempt to convert S-type data to 9-type data failed.

For example:

  1. A value to be treated as an error in the outside sign of the input format was input in the sign position of the input data.

  2. A value that was not specified in the zone sign of the input format was input in the zone position of the input data.

  3. A value other than a value from 0x0 to 0x9 is contained in the numeric position (the last four bits).

Action to take:

Check the input-side data file and the data format information.

10:

(No message detail)

Description:

An attempt to convert B-type data to 9-type data failed.

In the input format, the size set for the B-type is a value other than 2, 4, or 8.

Action to take:

Make sure that the input format data is registered. If you cannot register or see this data, the data format information might be corrupt. Collect data and management information, and then contact customer support.

11:

(No message detail)

Description:

An attempt to convert F-type data to 9-type data failed.

Either an infinite value or an invalid value is input in the input F-type data.

Action to take:

Check the input-side data file and the data format information.

12:

The Unicode byte order specified by the parameter file conflicts with BOM.

Description:

"0xFEFF" (BIG) is set in BOM of the input file, but "LITTLE" is set in the numeric byte order of the input file settings.

Action to take:

Check the input side data file and the numeric byte order of the input file settings of the parameter file.

13:

The Unicode byte order specified by the parameter file conflicts with BOM.

Description:

"0xFFFE" (LITTLE) is set in BOM of the input file, but "BIG" is set in the numeric byte order of the input file settings.

Action to take:

Check the input side data file and the numeric byte order of the input file settings of the parameter file.

15

The input data (%s) is not type Z.Check the following:

1. Whether a character other than numbers, symbols, decimal point, space, delimiters, and currency symbols is included in the data.

2. Whether the locations of the delimiter and decimal point are correct.

Description:

Invalid Z-type data was input.

Action to take:

Check the input-side data file and the data format information.

16:

The input data type (%c) contains a NULL character.

An error occurs if the character type contains a NULL character because of the settings in the environment settings file.

Description:

The input data contains the null character (0x00).

Action to take:

Check the settings of the environment settings file.

17:

An attempt to convert the input data (%s) to a date character string failed.

Description:

Invalid D-type data was input.

Action to take:

Check the input-side data file and the data format information.

50:

The delimiter value for output is not specified for the field name (%s).

You cannot preview the output if the delimiter value is not specified.

Description:

The output delimiter is not set.

Action to take:

Check the output delimiter settings.If the output delimiter is omitted, preview is not possible, but conversion can be performed.

51:

1001 fields occurred in the input.The maximum number of fields that can be processed is 1000.

Check whether the specified delimiter and line break code are the same as those in the input data.

Description:

The maximum number of fields that can be processed was exceeded.

Action to take:

The maximum number of fields is 1000.Check whether the specified delimiter and line break code are the same as those in the input data.

52:

The number of fields defined in CSVID (%s) is %d, but field %d occurred.

Description:

The format of the input file or matching file is "CSV", and the number of fields defined in the CSV format differs from the number of fields in the file.

For example, if 5 fields are defined in a CSV format, this error occurs if the input side has 6 file fields.

Action to take:

Check the input-side data file and the data format information.

55:

1001 fields occurred in the input.The maximum number of fields that can be processed is 1000.

Check whether the specified delimiter and line break code are the same as those in the input data.

Description:

The maximum number of fields that can be processed was exceeded.

Action to take:

The maximum number of fields is 1000.Check whether the specified delimiter and line break code are the same as those in the input data.

66:

No input data matches the field (%s).

Description:

The format of the input file or matching file is "CSV", and the number of fields defined in the CSV format differs from the number of fields in the file.

For example, if 5 fields are defined in a CSV format, this error occurs if the input side has 4 file fields.

Action to take:

Check the input-side data file and the data format information.