Options fields

This section explains the fields of the Options.

(1) Input behavior

Specify the handling of data during an input operation.

  • Character input to fields without CSV enclosure character

    Handling when data other than a numeric character string is used in a field not enclosed inside enclosure characters in a CSV format input file

    Allow

    : Data other than a numeric character string is handled as a character type.

    Do not allow

    : An error occurs if data other than a numeric character string is used.

    Note

    Fields enclosed in enclosure characters are fields in which data starts with an enclosure character. For example, when the enclosure character is a double quotation mark ("), "12 is treated as a field enclosed in enclosure characters, while 12" is treated as a character string.

    Furthermore, an input file format error occurs when "12 is converted because "12 does not end with an enclosure character.

     

  • Replacement of null characters with spaces:

    Select whether to replace with a halfwidth space when there is a Null value in the input file. This is enabled for format, multi format, and hierarchy format items.

    There are 4 data types: N, M, X, and D.

    Replace

    : Null values, if present in the input file, are replaced with halfwidth spaces.

    Do not replace

    : The input file is processed as is, even if it contains null values.

    For details about how to replace halfwidth spaces, see DataMagic Operation Manual.

    Note

    If there are null values in fullwidth character data that has control characters and shift codes, conversion to halfwidth spaces occurs unconditionally.

  • Handling of 0x40 in KEIS shift encoding:

    Handling when 0x40 is present in the shift code contained within the data of an input file that has KEIS as its Kanji code type

    Halfwidth space

    : 0x40 is converted to a halfwidth space.

    Most significant byte of two-byte code

    : 0x40 is handled as the most significant byte of 2-byte code.

    Fullwidth space

    : 0x40 is converted to a fullwidth space.

    Note

    When this field is set to Halfwidth space, it is executed without stopping the conversion of the input file containing the next data, even if Shift code of the input data contains an odd number of bytes is set in the Stop conditions.

    • This is for KEIS encoding data in which there is an odd number of bytes in the shift code due to the halfwidth space.

(2) Output behavior

Set the error condition during output and the file deletion condition.

  • Treat conversion of numeric values to character strings as an error:

    Handling when converting a numeric value to a character string. If this field is selected, conversion is not performed and an error occurs.

  • Treat conversion of character strings to numeric values as an error:

    Handling when converting a character string to a numeric value. If this field is selected, conversion is not performed and an error occurs.

    Note

    Character strings that meet the following conditions are not converted to numeric values and an error occurs, even if this field is not selected:

    • The value contains a fullwidth number.

    • The value contains a character other than a halfwidth number, decimal point (.), or minus sign (-).

    • The value contains multiple decimal points and minus signs.

    • There is a minus sign present in a position other than the beginning of a character string.

    • A decimal point is present at the beginning of the value.

  • Delete output file if output ends abnormally:

    Handling of output files when an abnormality occurs during output.

    When data processing is executed, if any of the following conditions are met, the output file is not deleted:

    • New is specified for Output file creation mode, and the output file already exists.

    • Use field values is specified for Output location.

    • Restore in case of error is selected.

(3) Stop conditions

The processing done when events such as numeric value area overflow and character area overflow occur during data processing.

 

  • Overflow in the numeric value area:

    Processing is stopped when there is a numeric value area overflow.

  • Overflow in the character area:

    Processing is stopped when there is a character area overflow.

  • ASCII present in type N:

    If N is specified for Field type in a condition where Shift JIS or EUC is selected as Kanji code type, the processing is stopped when a type N field contains an ASCII code.

    The specification is ignored when a format other than CSV is selected in the output settings and an identical value is selected as Kanji code type for both input settings and output settings.

  • Null character present in format character data:

    Processing is stopped when the input field type is M, N, X, or D, and when a null value is present inside the input data. If this field is selected, an error occurs when there is a null value in the data. Therefore, specifying Replacement of null characters with spaces for the input behavior is disabled.

  • Wrong database code type:

    Processing is stopped when the encoding of the connected database is different from Kanji code type for the input and the output settings of the data processing information.

  • Shift code of the input data contains an odd number of bytes:

    Processing is stopped when the input side encoding is an EBCDIC type and when there is an odd number of bytes within the shift code.

    However, checking for odd number of bytes is not performed when all the following conditions are met.

    1. Both input and output have an EBCDIC encoding type

    2. EBCDIC Set is the same

    3. The conversion of the input file containing the following data is executed without stopping, when Kana conversion, Alphanumeric conversion, and Symbol conversion is set to Do not convert in the Fullwidth and halfwidth character conversion, or when Halfwidth space is selected for Handling of 0x40 in KEIS shift encoding.

      • This is for KEIS encoding data in which there is an odd number of bytes in the shift code due to the halfwidth space.

= Remarks =
  • For details about the overflows, see DataMagic Operation Manual.

  • If the output format is Database Table in the following cases,

    a conversion error might occur and the processing might stop because of non-application of Overflow in the numeric value area and Overflow in the character area settings:

    1. Size overflow due to code conversion when the database table kanji code type is different

    2. Maximum size overflow in variable length fields

    3. Too much numeric value data accuracy

(4) Tuning

Specifies whether to execute this data processing information by using multithreading.

  • Use the specified system environment settings

    Follows the specification of Use multithreading on the General tab of the System Environment Settings screen.

  • Use

    Uses multithreading.

  • Do not use

    Does not use multithreading.

Note

The multithreading setting is enabled according to the order of priority shown below. When high-priority settings are executed, low-priority settings are ignored.

  1. Arguments of the utled command (-thread)

  2. Options in the Data Processing Settings screen

  3. Tuning of system environment settings

(5) User exit program

The user exit program name used in data processing.

Specify with absolute path or relative path.

Click the Browse button to display the Select File dialog box and select any programs.

(6) Input formats for dates

Specify input formats for dates. When you double-click a field or the Edit icon, a screen appears and prompts you to set input formats for dates.

Either select input formats from the samples, or manually enter date formats. Specify the character strings for the input format for dates in uppercase letters. You can specify up to 10 input formats for dates.

The following table provides a list of input formats:

Table 2.52 List of Input Formats

#

Character string

Description

1

YYYY

Western calendar year (four digits)

2

YY

Western calendar year (last two digits) Note that the year is assumed to be in the 2000s.

For example, if YY is 14, the year is 2014.

3

RR

Western calendar year (last two digits)

If the value is 69 or larger, the year is assumed to be in the 1900s. If the value is 68 or smaller, the year is assumed to be in the 2000s.

4

EYY

Abbreviated form of Japanese era name and Japanese calendar year (00 to 99) (for example, T09 or S25)

5

EEYY

Japanese era name and Japanese calendar year (00 to 99) (for example, 大正09 or 昭和25)

6

eyy

Abbreviated form of Japanese era name and Japanese calendar year (0 to 99) (for example, T9 or S25)

7

eeyy

Japanese era name and Japanese calendar year (0 to 99) (for example, 大正9 or 昭和25)

8

MM

Month (01 to12)

9

mm

month (1 to 12)

10

DD

Day (01 to 31)

11

dd

day (1 to 31)

12

HH or HH24

Hour (00 to 23)

13

hh or hh24

hour (0 to 23)

14

HH12

Hour (01 to 12)

15

hh12

hour (1 to 12)

16

MI

Minute (00 to 59)

17

mi

minute (0 to 59)

18

SS

Second (00 to 59)

19

ss

second (0 to 59)

20

MON

English abbreviation of a month. All uppercase (for example, JAN).

21

Mon

English abbreviation of a month. Initial letter uppercase (for example, Jan).

22

mon

English abbreviation of a month. All lowercase (for example, jan).

23

MONTH

English name of month. All uppercase (for example, JANUARY).

24

Month

English name of month. Initial letter uppercase (for example, January).

25

month

English name of month. All lowercase (for example, january).

26

AM

AM: morning or PM: afternoon

27

Am

Am: morning or Pm: afternoon

28

am

am: morning or pm: afternoon

29

A.M.

A.M.: morning or P.M.: afternoon

30

a.m.

a.m.: morning or p.m.: afternoon

= Remarks =

For DataMagic to support a Japanese era name that is more recent than 平成, it is necessary to specify the new Japanese era name in the Japanese era name (era_name) field of the system environment settings file (huledenv.conf).

Note

You cannot use a combination of a format that indicates AM or PM (such as AM, Am, or am) and a 24-hour time format (HH or hh) in a single date format setting. If you use such a combination, data processing may not be executed correctly.

Use a combination of a format that indicates AM or PM and a 12-hour time format (HH12 or hh12).