Messages and limitations of the Fixed-Length connector

Corresponding error

• None

Corresponding error

• StructuredTextParseException

Corresponding error

• IllegalPaddingException

Corresponding error

• java.lang.ArithmeticException

Specification limits

• About naming conventions

  • If elements with the same name exist in a parent element, data can't be read properly.

    Specifically, it applies for the following elements:

    • Groups

    • Records directly under the structure definition icon

    • Records in the same group

    • Fields in the same record

  • The names of fields, records, and groups are required.

• About the number of occurrences for group/record

  • If Occurrence of the group is Unlimited, when the input data corresponding to that group appears, the data is first parsed using the next group to check whether it's applicable. If applicable, the next group is applied. If not applicable, parsing using that group is performed.

  • If Occurrence of the record is Unlimited, when the input data corresponding to that record appears, the data is first parsed using that record to check whether it's applicable. If applicable, parsing using that record continues. If not applicable, parsing using the next record is performed.

  • If Occurrence of the record or the group is Unlimited, the actual maximum value is the value of Integer.MAX_VALUE of Java, which is 2147483647.

  • If Omittable is selected for Occurrence of the group, no error occurs even when the actual number of occurrences of the group is fewer than the specified number of occurrences.

  • If Omittable is selected for Occurrence of the record, no error occurs even when the actual number of occurrences of the record is fewer than the specified number of occurrences.

• About the field length

  • The length of the field is specified in bytes. The byte length depends on the specified encoding.

  • The maximum value for the field length is 9999.

• About the date type field

  • Strings such as the day of the week that appear in a date are dependent on the default locale. If you want to use date data which can't be parsed by the default locale, ensure the data is read as a string.

• About mass data processing

  • Read data is output for each group. Therefore, when there's a large amount of data contained in the records in the group, OutOfMemoryError may occur.

• Others

  • Custom characters aren't supported.

  • When a field that exists in Column list is deleted in Structure definition, the field remains in Column list.

  • If you select a group in Structure definition to add a field to Column list, the order of the fields can't be guaranteed.

  • Data that doesn't contain tags or newline codes and has an unspecified number of occurrences can't be accurately analyzed because the criteria for switching the structural analysis can't be determined.

  • "Transaction" that is output to execution logs is implicitly defined to organize the structure of the group and has an unlimited number of occurrences.

Specification limits

• Custom characters aren't supported.

• When writing, if the length of the data is insufficient for a field of a specified length due to string manipulation (e.g. padding, left or right alignment), the remainder of the field is filled with padding characters.

• String manipulations (e.g. padding, left or right alignment) are applied after all data is temporarily converted to "Unicode". Therefore, depending on the character code, the result may not be as expected.

• When writing in UTF-16, a BOM (Byte Order Mark) is added to the beginning of each field.

• When writing in EBCDIC (Cp930), multibyte characters are enclosed by a control character "Shift-OUT (0x0e)" that indicates the change to multibyte characters, and a control character "Shift-IN (0x0f)" (1 byte each) that indicates the change back to single-byte characters.

• When writing in EBCDIC (Cp930), if multibyte character (such as double-byte space) is used for padding, "Shift-OUT (0x0e)" and "Shift-IN (0x0f)" are appended for each padding character.

• When the number of fields defined in the column list is greater than the number of columns in the XML data of the input source, an error occurs and writing fails.

• If null is input, it's written as an empty string.

• You can edit the values of the nodes in the structure definition tree by double-clicking the nodes.

• You can't add, delete, or copy nodes in the structure definition tree.

• Numeric (zoned decimal) and numeric (packed decimal) field types can't be defined in the structure definition file.

• When you import the structure definition file, the padding mode is "Direct".

• When you set packed decimal for the field type, the child node "Zone nibble" appears, but this setting isn't used.

• "Transaction" that is output to execution logs is implicitly defined to organize the structure of the group and has an unlimited number of occurrences.

• If elements with the same name exist in a parent element, data can't be written properly.

  Specifically, it applies for the following elements:

  • Groups

  • Records directly under the structure definition icon

  • Records in the same group

  • Fields in the same record

Specification limits

• Custom characters aren't supported.

• String manipulations (e.g. suppress, left or right alignment) are applied after all data is temporarily converted to "Unicode". Therefore, depending on the character code, the result may not be as expected.

• A group can't contain itself (a group can't be nested). Records are the only components of a group.

• Elements with the same parent element can't have the same name.

  Specifically, it applies for the following elements:

  • Groups

  • Records directly under the structure definition icon

  • Records in the same group

  • Fields in the same record

• The names of fields, records, and groups are required.

• Tags are handled as strings. Tags don't support other types.

• When blank lines appear in the middle of the file to read, an error will occur. However, when a blank line appears at the end of the file to read, the blank line will be ignored.

• Strings such as the day of the week that appear in a date are dependent on the default locale. If you want to use date data which can't be parsed by the default locale, ensure the data is read as a string.

• If Occurrence of the group is Unlimited, when the input data corresponding to that group appears, the data is first parsed using the next group to check whether it's applicable. If applicable, the next group is applied. If not applicable, parsing using that group is performed.

• If Occurrence of the record is Unlimited, when the input data corresponding to that record appears, the data is first parsed using that record to check whether it's applicable. If applicable, parsing using that record continues. If not applicable, parsing using the next record is performed.

• If Occurrence of the record or the group is Unlimited, the actual maximum value is the value of Integer.MAX_VALUE of Java, which is 2147483647.

• If Omittable is selected for Occurrence of the group, no error occurs even when the actual number of occurrences of the group is fewer than the specified number of occurrences.

• If Omittable is selected for Occurrence of the record, no error occurs even when the actual number of occurrences of the record is fewer than the specified number of occurrences.

• The maximum value for the field length is 9999.

• When a field that exists in the column list is deleted in the structure definition, the field remains in the column list.

• If you select a group in the structure definition to add a field to the column list, the order of the fields can't be guaranteed.

• The length of the field is specified in bytes. The byte length depends on the specified encoding.

• The order of the fields in the column list follows the order of the fields which appear in the structure definition from the top. If you change the order of the fields in the column list, they can't be read correctly.

• If you export or import a structure definition in which a record (A record) is in the same hierarchy as a certain group (A group), and is in a lower position than the group, A record becomes a child element of A group.

  Example:

  

• Characters that need to be escaped in regular expressions such as "[" or "]" can't be used in a group name, a record name, or a field name.

• If Suppressed character is an empty character, the suppression processing isn't performed.

Specification limits

• Custom characters aren't supported.

• When writing, if the length of the data is insufficient for a field of a specified length due to string manipulation (e.g. padding, left or right alignment), the remainder of the field is filled with padding characters.

• String manipulations (e.g. padding, left or right alignment) are applied after all data is temporarily converted to "Unicode". Therefore, depending on the character code, the result may not be as expected.

• The field name is required.

• Tags are handled as strings. Tags don't support other types.

• When the number of fields defined in the column list is fewer than the number of columns in the XML data of the input source, only the data for the fields defined in the column list will be written.

• When the number of fields defined in the column list is greater than the number of columns in the XML data of the input source, an error occurs and writing fails.

• The maximum value for the field length is 9999.

• The length of the field is specified in bytes. The byte length depends on the specified encoding.

• Newline characters are written with the Encoding in the Write Settings in the Write Fixed-Length File operation.

• The starting positions of the fields in the structure definition are calculated based on the length of the fields added to the parent record. The starting positions of the fields in the column list are calculated based on the length of the fields added to the column.

• If you export or import a structure definition in which a record (A record) is in the same hierarchy as a certain group (A group), and is in a lower position than the group, A record becomes a child element of A group.

  Example:

  

• Characters that need to be escaped in regular expressions such as "[" or "]" can't be used in a group name, a record name, or a field name.

• Slashes ("/") can't be used in a field name.

• When Padding mode is "Direct", you need to specify one or more bytes of padding characters.

• Elements with the same parent element can't have the same name.

  Specifically, it applies for the following elements:

  • Groups

  • Records directly under the structure definition icon

  • Records in the same group

  • Fields in the same record