Property | S/T | Description |
StartOffset | S | If your source data file starts with characters that need to be excluded from the transformation, set the StartOffset option to specify at which byte of the file to begin. The default value is zero. The correct value may be determined by using the Hex Browser. For a list of the 256 standard and extended ASCII characters, search for "hex values" in the documentation. Note: This property is set in number of bytes, not characters. |
RecordSeparator | ST | When a binary sequential file is your connector and you are using a 01 copybook to define the fields, you may have a record separator at the end of each record. If so, you may specify the record separator here. This causes the integration platform to automatically ignore the record separator when it reads the source data. The default is "None". The available list of separators are None (default), carriage return-line feed, line feed, carriage return, line feed-carriage return, form feed, and empty line. |
CodePage | ST | This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US. |
Property | S/T | Description |
RecordSeparator | ST | LF(000A) – default CR(000D) |
JobScript | T | Optional. Enter a text file name to create a flat file that can be uploaded to a Teradata data warehouse database. The integratin platform automatically creates a text file that contains a script that the Teradata FastLoad Utility can understand, making it faster than typing in the script by hand. You must modify the Database ID, User name and Password to execute the script. FastLoadTable – optional. Enter a table name here. If you do not, a default name is provided, called Table1. |
FastLoadTable | T | Enter a table name here. If you do not, a default name is provided, called Table1. |
Property | S/T | Description |
ByteOrder | S | Allows you to specify the byte order of Unicode (wide) characters. The default is Auto and is determined by the architecture of your computer. The list box options are Auto (default), Little Endian, and Big Endian. Little Endian byte order is generally used by Intel machines and DEC Alphas and places the least significant portion of a byte value in the left portion of the memory used to store the value. Big Endian byte order is used by IBM 370 computers, Motorola microprocessors and most RISC-based systems and stores the values in the same order as the binary representation. |
ElementSeparator | S | This is a complete list of Element Separators from which you can choose from the list: • CR-LF • SOH (0001) • STX (0002) • ETX (0003) • EOT (0004) • ENQ (0005) • ACK (0006) • BEL (0007) • BS (0008) • HT (0009) • LF (000A) |
• VT (000B) • FF (000C) • CR (000D) • SO (000E) • S1 (000F) • DLE (0010) • DC1 (0011) • DC2 (0012) • DC3 (0013) • DC4 (0014) • NAK (0015) | ||
• SYN (0016) • ETB (0017) • CAN (0018) • EM (0019) • SUB (001A) • ESC (001B) • FS/IS4 (001C) • GS/IS3 (001D) • RS/IS2 (001E) • US/IS1 (001F) • SP (0020) | ||
• ! (0021) • " (0022) • # (0023) • $ (0024) • % (0025) • & (0026) • ' (0027) • ( (0028) • ) (0029) • * (002A) | ||
• + (002B) - Default • , (002C) • - (002D) • . (002E) • / (002F) • : (003A) • ; (003B) • < (003C) • = (003D) • > (003E) • ? (003F) | ||
• @ (0040) • [ (005B) • \ (005C) • ] (005D) • ^ (005E) • _ (005F) • ' (0060) • { (007B) • (007C) • } (007D) • ~ (007E) • DEL (007F) | ||
SegmentTerminator | S | In this property, you may select a Segment Terminator from the list. (See the ElementSeparator list, above, for your options). |
SourceScriptFile | S | The script file used for the source structure. To change the script file, enter the new file and click OK. |
Encoding | S | This allows you to select the type of encoding used with your source and target files. Encoding Notes Shift-JIS encoding is meaningful only in Japanese operating systems. UCS-2 is no longer considered a valid encoding name, but you may use UCS2. Open the data file with a text editor and change UCS-2 to UCS2. |
DatatypeSet | T | Allows you to choose between standard and COBOL data types in your fixed ASCII data file. Standard is the default and means that all the data in the file is readable (lower) ASCII data. If your fixed ASCII file contains (or needs, for a target file) COBOL display type fields and you are using a COBOL 01 copybook (fd) to define the fields, you MUST change this property option to "COBOL" before connecting to the COBOL copybook in the External Structured Schema window. |
FieldSeparator | T | Allows you to choose a field separator character for your target file. The default is None. The other choices are comma (,), tab, space, carriage return-line feed (CR-LF), line feed (LF), carriage return (CR), line feed-carriage return (LF-CR), control-R, and pipe ( | ). If the record separator is not one of the choices from the list and is a printable character, highlight None and then type the correct character. For example, if the separator is an asterisk ( * ), type an asterisk from the keyboard. If the record separator is not a printable character, replace None with a backslash, an X, and the hexadecimal value for the separator. For example, if the separator is a check mark, then enter \XFB. For a list of the 256 standard and extended ASCII characters, search for "hex values" in the documentation. |
FillFields | T | Writes an ASCII data file where every field is variable length. If this property is set to false, all trailing spaces are removed from each field when the data is written. The default is true. The true setting pads all fields with spaces to the end of the field length to maintain the fixed length of the records. |
RaggedRight | T | Writes an ASCII data file where the last field in each record is variable length when set to true. The default is false. The false setting pads the last field with spaces to the end of the record length to maintain the fixed length of the records. |
RecordSeparator | T | A fixed ASCII file is presumed to have a carriage return-line feed (CR-LF) between records. To use other characters as the record separator or no record separator, click the RecordSeparator cell and click once. Then click the down arrow to the right of the box and click the desired record separator in the list box. The choices are carriage return-line feed (default), line feed, carriage return, line feed-carriage return, form feed, empty line and no record separator. To use a separator other than one from the list, you can type it here. If the record separator is not one of the choices from the list and is a printable character, highlight the CR-LF and then type the correct character. For example, if the separator is a pipe ( | ), type a pipe from the keyboard. If the record separator is not a printable character, replace CR-LF with a backslash, an X, and the hexadecimal value for the separator. For example, if the separator is a check mark, then enter \XFB. For a list of the 256 standard and extended ASCII characters, search for "hex values" in the documentation. |
TabSize | T | If your source fixed ASCII file has embedded tab characters representing white space, you can expand those tabs to set a number of spaces. The default value is zero. To change it, highlight the zero and type a new value. |
CodePage | T | This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US. |
Property | S/T | Description |
ByteOrder | S | Allows you to specify the byte order of Unicode (wide) characters. The default is Auto and is determined by the architecture of your computer. The list box options are Auto (default), Little Endian. and Big Endian. Little Endian byte order is generally used by Intel machines and DEC Alphas and places the least significant portion of a byte value in the left portion of the memory used to store the value. Big Endian byte order is used by IBM 370 computers, Motorola microprocessors and most RISC-based systems and stores the values in the same order as the binary representation. |
ElementSeparator | S | The following element separators are available: • CR-LF • SOH (0001) • STX (0002) • ETX (0003) • EOT (0004) • ENQ (0005) • ACK (0006) • BEL (0007) • BS (0008) • HT (0009) • LF (000A) |
• VT (000B) • FF (000C) • CR (000D) • SO (000E) • S1 (000F) • DLE (0010) • DC1 (0011) • DC2 (0012) • DC3 (0013) • DC4 (0014) | ||
• NAK (0015) • SYN (0016) • ETB (0017) • CAN (0018) • EM (0019) • SUB (001A) • ESC (001B) • FS/IS4 (001C) • GS/IS3 (001D) • RS/IS2 (001E) • US/IS1 (001F) • SP (0020) | ||
• ! (0021) • " (0022) • # (0023) • $ (0024) • % (0025) • & (0026) • ' (0027) • ( (0028) • ) (0029) • * (002A) | ||
• + (002B) - Default • , (002C) • - (002D) • . (002E) • / (002F) • : (003A) • ; (003B) • < (003C) • = (003D) • > (003E) • ? (003F) | ||
• @ (0040) • [ (005B) • \ (005C) • ] (005D) • ^ (005E) • _ (005F) • ' (0060) • { (007B) • (007C) • } (007D) • ~ (007E) • DEL (007F) | ||
SegmentTerminator | S | In this property, you may select a Segment Terminator from the list. (See the ElementSeparator list, above, for your options). |
SourceScriptFile | S | The script file used for the source structure. To change the script file, enter the new file name and click OK. |
Encoding | S | This allows you to select the type of encoding used with your source and target files. Encoding Notes Shift-JIS encoding is meaningful only in Japanese operating systems. UCS-2 is no longer considered a valid encoding name, but you may use UCS2. Open the data file with a text editor and change UCS-2 to UCS2. |
DatatypeSet | T | Allows you to choose between standard and COBOL data types in your fixed ASCII data file. Standard is the default and means that all the data in the file is readable (lower) ASCII data. If your fixed ASCII file contains (or needs, for a target file) COBOL display type fields and you are using a COBOL 01 copybook (fd) to define the fields, you MUST change this property option to "COBOL" before connecting to the COBOL copybook in the External Structured Schema window. |
FieldSeparator | T | Allows you to choose a field separator character for your target file. The default is None. The other choices are comma (,), tab, space, carriage return-line feed (CR-LF), line feed (LF), carriage return (CR), line feed-carriage return (LF-CR), control-R, and pipe ( | ). If the record separator is not one of the choices from the list and is a printable character, highlight None and then type the correct character. For example, if the separator is an asterisk ( * ), type an asterisk from the keyboard. If the record separator is not a printable character, replace CR-LF with a backslash, an X, and the hexadecimal value for the separator. For example, if the separator is a check mark, then enter \XFB. For a list of the 256 standard and extended ASCII characters, search for "hex values" in the documentation. |
FillFields | T | Writes an ASCII data file where every field is variable length. If this property is set to false, all trailing spaces are removed from each field when the data is written. The default is true. The true setting pads all fields with spaces to the end of the field length to maintain the fixed length of the records. |
RaggedRight | T | Writes an ASCII data file where the last field in each record is variable length when set to true. The default is false. The false setting pads the last field with spaces to the end of the record length to maintain the fixed length of the records. |
RecordSeparator | T | A fixed ASCII file is presumed to have a carriage return-line feed (CR-LF) between records. To use other characters as the record separator or no record separator, click the RecordSeparator cell and click once. Then click the down arrow to the right of the box and click the desired record separator in the list box. The choices are carriage return-line feed (default), line feed, carriage return, line feed-carriage return, form feed, empty line and no record separator. To use a separator other than one from the list, you can type it here. If the record separator is not one of the choices from the list and is a printable character, highlight the CR-LF and then type the correct character. For example, if the separator is a pipe ( | ), type a pipe from the keyboard. If the record separator is not a printable character, replace CR-LF with a backslash, an X, and the hexadecimal value for the separator. For example, if the separator is a check mark, then enter \XFB. For a list of the 256 standard and extended ASCII characters, search for "hex values" in the documentation. |
TabSize | T | If your source fixed ASCII file has embedded tab characters representing white space, you can expand those tabs to set a number of spaces. The default value is zero. To change it, highlight the zero and then type a new value. |
CodePage | T | This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US. |
Property | S/T | Description |
AlternateFieldSeparator | S | Most data files have only one field separator between all the fields; however, it is possible to have more than one field separator. If your source file has one field separator between some fields and a different separator between other fields, you can specify the second field separator here. Otherwise, you should leave this set to None (the default). The alternate field separators available from the list are none (default), comma, tab, space, carriage return-line feed, line feed, carriage return, line feed-carriage return, ctrl-R, and pipe (|). To select a separator, click AlternateFieldSeparator. Then click the arrow to the right of the box to choose from the list of available separators. If you have an alternate field separator other than one from the list, you can type it here. If the field separator is not a printable character, replace CR-LF with a backslash, an X, and the hexadecimal value for the separator. The Unicode connectors read the data from the file as Unicode and look for the Unicode characters specified as the separators to break up the data into fields or records. Then, the actual Unicode data is assigned to fields or records. |
AutomaticStyling | S | AutomaticStyling changes the way Unicode data is read or written. By default, AutomaticStyling is set to false, causing all data to be read or written as Text. When set to true, it determines and formats (automatically) particular data types, such as numeric and date fields. AutomaticStyling insures, for example, that a date field in a Unicode source file is formatted as a date field in the target file, and not as a character or as text data. Note: If a source file contains zip codes, you may want to leave AutomaticStyling to false so that the leading zeros in some zip codes in the eastern United States are not deleted. Note: For a Unicode target file, if you set FieldDelimitStyle to Text, you must also set AutomaticStyling to true so that delimiters are placed around only the nonnumeric fields. |
ByteOrder | ST | Allows you to specify the byte order of Unicode (wide) characters. The default is Auto and is determined by the architecture of your computer. The list box options are Auto (default), Little Endian and Big Endian. Little Endian byte order is generally used by Intel machines and DEC Alphas and places the least significant portion of a byte value in the left portion of the memory used to store the value. Big Endian byte order is used by IBM 370 computers, Motorola microprocessors and most RISC-based systems and stores the values in the same order as the binary representation. |
EmptyFieldsNull | S | Allows you to treat all empty fields as null. |
Encoding | ST | Type of encoding to use with source and target files. |
Field1IsRecTypeId | S | If the first field of each record in your source file contains the Record Type ID, you can select true for this property and the integration platform treats each record as a separate record type. Within each record, field names derived from the Record Type ID are automatically generated for each field. For details, see
Field1IsRecordType. |
FieldDelimitStyle | T | When Unicode (Delimited) is your connector, this option determines whether the specified FieldStartDelimiter and the FieldEndDelimiter is used for all fields, only for fields containing a separator, or only for text fields, as follows: • All – Places the delimiters specified in FieldStartDelimiter and FieldEndDelimiter before and after every field. Default setting is All. For example: "Smith","12345","Houston". • Partial – Places the specified delimiters before and after fields only where necessary. A field that contains a character that is the same as the field separator would have the field delimiters placed around it. A common example is a memo field that contains quotes within the data: "Customer responded with "No thank you" to my offer" • Text – Places delimiters before and after text and name fields (non-numeric fields). Numeric and date fields have no FieldStartDelimiter or FieldEndDelimiter. For example: "Smith", 12345,"Houston", 11/13/04 • Non-numeric – Places delimiters before and after all nonnumeric types, such as date fields. An important difference between non-numeric and text is that non-numeric delimits date fields, while text does not. |
FieldEndDelimiter | ST | Delimited Unicode files are presumed to have beginning-of-field and end-of-field delimiters. The default delimiter is a quotation mark because it is the most common. However, some files do not contain field delimiters, so this option is available for both source files and target files. To read from or write to a file with no delimiters, set FieldStartDelimiter to none. |
FieldSeparator | ST | A delimited Unicode file is presumed to have a comma between each field. To specify some other field separator, click once in the FieldSeparator Current Value box. Then click the down arrow to the right of the box to display the list of options. The list box options are comma (default), tab, space, carriage return-line feed, linesep, line feed, carriage return, line feed-carriage return, a pipe (|), and no field separator. If you have or need an alternate field separator other than one from the list, you can type it here. If the field separator is not a printable character, replace CR-LF with a backslash, an X, and the hexadecimal value for the separator. The Unicode connectors read the data from the file as Unicode and look for the Unicode characters specified as the separators to break the data up into fields or records. Then the actual Unicode data is assigned to fields or records. |
FieldStartDelimiter | ST | Delimited Unicode files are presumed to have beginning-of-field and end-of-field delimiters. The default delimiter is a quotation mark because it is the most common. However, some files do not contain field delimiters, so this option is available for both your source files and your target files. To read from or write to a file with no delimiters, set FieldEndDelimiter to none. |
Header | ST | In some files, the first record is a header record. For source data, you can remove it from the input data and cause the header titles to be used automatically as field names. For target data, you can cause the field names in your source data to automatically create a header record in your target file. To identify a header record, set Header to true. The default is false. Note: If your target connector is Unicode (Delimited) and you are appending data to an existing file, leave Header set to false. |
MaxDataLen | T | When Unicode (Delimited) is your target connector, this option allows you to specify the maximum number of characters to write to a field. If this value is set to 0 (the default), the number of characters written to a field is determined by the field length. If you set this value to a number other than zero, data may be truncated. |
NullIndicator | ST | This property allows you to enter a special string used to represent null values. You can select predefined values or type any other string. • Target – When writing a null value, the contents of the null indicator string are written. • Source – A check is made to see if the null indicator is set. If it is set, the data is compared to the null indicator. If the data and the null indicator match, the field is set to null. |
NumericFormatNormalization | S | Setting this property to true handles thousands-separators according to usage for locale when numeric strings are converted to numeric type. This property overrides any individual field settings. Supported in 9.2.2 and later. Default is false. |
OrderMark | T | The Order Mark is a special character value sometimes written to a Unicode text file to indicate the byte order used for encoding each of the Unicode characters. In the integration platform, you have the option of writing byte order mark at the beginning of Unicode (wide) output or not. The default is false. If you wish to have the byte order mark placed at the beginning of your output, change this option to true. |
RecordFieldCount | S | If your source data file has field separators but no record separator, or if it has the same separator for both the fields and the records, you should specify the RecordSeparator (most likely a blank line), leave the AlternateFieldSeparator option blank and enter the exact number of fields per record in this box. The default value is zero. |
RecordSeparator | ST | A delimited Unicode file is presumed to have a carriage return-line feed (CR-LF) between records. To use other characters for a record separator, click RecordSeparator for a list of choices, including system default, carriage return-line feed (default), line feed, carriage return, line feed-carriage return, form feed, empty line, ctrl-E, and no record separator. To use a separator other than one from the list, enter it here. The SystemDefault setting enables the same transformation to run with CR-LF on Windows systems and LF on Unix systems without having to change this property. If the record separator is not a printable character, replace CR-LF with a backslash, an X, and the hexadecimal value for the separator. The Unicode connectors read the data from the file as Unicode and look for the Unicode characters specified as the separators to break the data up into fields or records. Then the actual Unicode data is assigned to fields or records. |
StartOffset | If your source data file starts with characters that need to be excluded from the transformation, set the StartOffset option to specify at which byte of the file to begin. The default value is zero. The correct value may be determined by using the Hex Browser. Note: This property is set in number of bytes, not characters. | |
StripLeadingBlanks | ST | For a Unicode source file, by default the integration platform leaves leading blanks in delimited Unicode data. If you want to delete the leading blanks, set StripLeadingBlanks to true. For a Unicode target file, by default, the integration platform strips leading blanks in delimited Unicode data. If you want to leave the leading blanks, set StripLeadingBlanks to false. |
StripTrailingBlanks | ST | For a Unicode source file, by default the integration platform keeps trailing blanks in the data. If you want to delete the trailing blanks, set StripTrailingBlanks to true. For a Unicode target file, by default the integration platform strips trailing blanks in the data. If you want to leave the trailing blanks, set StripTrailingBlanks to false. The field options that you may change are listed below. |
StyleSampleSize | S | Sets the number of records (starting with record 1) that are analyzed to set a default width for each source field. The default value for this option is 5000. You can change the value to any number between 1 and the total number of records in your source file. As the number gets larger, more time is required to analyze the file, and it may be necessary to analyze every record to ensure that no data is truncated. To change the value, click the StyleSampleSize Current Value box, highlight the default value and type a new value. |
TransliterationIn | T | Allows you to specify a character, or a set of characters, to be filtered out of the source data. For any character in TransliterateIn, the corresponding character from the TransliterateOut property is substituted. If there is no corresponding character, the source character is filtered out completely. TransliterateIn supports C-style escape sequences such as \n (new line), \r (carriage return) and \t (tab). |
TransliterationOut | T | Allows you to specify a character to be substituted for another character from the source data. For any character in TransliterateIn, the corresponding character from the TransliterateOut property is substituted. If you wish the source character to be filtered out completely, leave this field blank. If there are no characters to be transliterated, this field should be left blank. The TransliterateOut property supports C-style escape sequences such as \n (new line), \r (carriage return) and \t (tab). |
Names_01 | Names_02 | Names_03 | Names_04 | Names_05 | Names_06 | Names_07 |
Names | Arnold | Benton | Cassidy | Denton | Exley | Fenton |
Property | S/T | Description |
ByteOrder | ST | Allows you to specify the byte order of Unicode (wide) characters. The default is Auto and is determined by the architecture of your computer. The list box options are Auto (default), Little Endian and Big Endian. Little Endian byte order is generally used by Intel machines and DEC Alphas and places the least significant portion of a byte value in the left portion of the memory used to store the value. Big Endian byte order is used by IBM 370 computers, Motorola microprocessors and most RISC-based systems and stores the values in the same order as the binary representation. |
CharFieldWidths | ST | Allows you to set field width by number of characters or number of bytes. With MBCS characters, a character may take more than one byte; files may have columns fixed by number of characters regardless of the number of bytes or may have columns fixed by number of bytes (variable number of characters). If truncation occurs in a column, the last double-byte character is replaced by a single-byte padding character. The default is false. False sets the field width by number of bytes. true sets the field width by number of characters. |
DatatypeSet | ST | Allows you to choose standard or COBOL data types in a Unicode (Fixed) data file. Standard is default and means that all data in the file is readable. If your Unicode (Fixed) file contains (or needs, for target file) COBOL display type fields and you are using a COBOL 01 copybook (fd) to define the fields, you must change this property option to COBOL before connecting to the COBOL copybook in the External Structured Schema window. |
Encoding | ST | Type of encoding to use with source and target files. For details, see
Additional Information About Encoding. |
FieldSeparator | T | Allows you to choose a field separator character for your target file. The default is None. The choices are None (default), coma, tab, space, carriage return-line feed, line feed, carriage return, line feed-carriage return, control-R, and pipe (|). If the alternate field separator is not one of the listed choices and is a printable character, see
Alternate Tip on FieldSeparator Property. |
Fill Fields | T | Allows writing a Unicode (Fixed) data file where every field is variable length. If this property is set to false, all trailing spaces are removed from each field when the data is written. The default is true. The true setting pads all fields with spaces to the end of the field length to maintain the fixed length of the records. |
InsertEOFRecSep | S | This option inserts a record separator on the last record of the file, if it is missing. The default is false. If set to true, this property captures the last record (with no record separator) instead of discarding it. |
NumericFormatNormalization | S | Setting this property to true handles thousands-separators according to usage for locale when numeric strings are converted to numeric type. This property overrides any individual field settings. Default is false. |
Order Mark | T | The Order Mark is a special character value that is sometimes written to a Unicode text file to indicate the byte order used for encoding each of the Unicode characters. In the integration platform, you have the option of writing byte order mark at the beginning of Unicode (wide) output or not. The default is false. If you wish to have the byte order mark placed at the beginning of your output, change this option to true. |
Ragged Right | T | Writes a data file where the last field in each record is variable length when set to true. The default is false. The false setting pads the last field with spaces to the end of the record length to maintain the fixed length of the records. You must set FillFields to false for the RaggedRight property to work properly. The Ragged Right property has no effect if you set FillFields to true. If FillFields is false, then the RaggedRight property determines whether blank fields and fields with only spaces as data appears at the end of the record. |
RecordSeparator | ST | A Unicode (Fixed) file is presumed to have a carriage return-line feed (CR-LF) between records. To specify other characters to separate records, click RecordSeparator for a list of choices, including system default, carriage return-line feed (default), line feed, carriage return, line feed-carriage return, form feed, empty line, ctrl-E, and no record separator. To use a separator other than one from the list, enter it here. The SystemDefault setting enables the same transformation to run with CR-LF on Windows systems and LF on Unix systems without having to change this property. If your field or record separator is not listed, highlight the default separator. Enter the characters you wish to use as a separator. The Unicode connectors read the data from the file as Unicode and look for the Unicode characters specified as the separators to break the data up into fields or records. Then the actual Unicode data is assigned to fields or records. |
Sample Size | S | Set the number of records (starting with record 1) that are analyzed to set a default width for each source field. The default is 1000. You can change the value to any number between 1 and the total number of records in your source file. As the number gets larger, more time is required to analyze the file, and it may be necessary to analyze every record to ensure no data is truncated. To change the value, click the Sample Size Current Value box, highlight the default value and type a new value. |
StartOffset | S | If your source data file starts with characters that need to be excluded from the transformation, set the StartOffset option to specify at which byte of the file to begin. The default value is zero. The correct value may be determined by using the Hex Browser. For a list of the 256 standard and extended ASCII characters, search for "hex values" in the documentation. This property is set in number of bytes, not characters, regardless of the CharFieldWidths property setting. |
StripLeadingBlanks | S | For a Unicode source file, by default, leading blanks are left in Unicode (Fixed) data. To delete leading blanks, click the StripLeadingBlanks Current Value box and click once. Then click the down arrow to the right of the box and click true. |
StripTrailingBlanks | S | By default, trailing blanks are left in Unicode (Fixed) data. To delete trailing blanks, click the StripTrailingBlanks Current Value box and click once. Then click the down arrow to the right of the box and click true. |
Tab Size | ST | If your source or target Unicode (Fixed) file has embedded tab characters representing white space, you can expand those tabs to set a number of spaces. The default value is zero. |
Property | S/T | Description |
CodePage | S | This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US. |
Property | S/T | Description |
MaxRecordLength | S | This specifies the maximum record length of the data. The default is 32700 bytes. |
ShortLastRecord | S | If set to true, short reads are ignored on the last record of the file. In other words, the last record is processed even if the End of File (EOF) is reached before reading the end of the record. The default is false. |
StartOffset | S | If your source data file starts with characters that need to be excluded from the transformation, set the StartOffset option to specify at which byte of the file to begin. The default value is zero. The correct value may be determined by using the Hex Browser. For a list of the 256 standard and extended ASCII characters, search for "hex values" in the documentation. Note: This property is set in number of bytes, not characters. |
OccursPad | S | When using COBOL files, you may have fields of variable length. If so, you may specify how to fill the field with pads to a fixed length. The default is None. The following options are available: • None (which leaves the fields uneven) – Default • End of Record (which fills the remainder of the record with your specified pad character) • Within Group (which fills the field with your specified pad character) |
CodePage | ST | This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US. |
Property | S/T | Description |
MaxRecordLength | S | This specifies the maximum record length of the data. The default is 32700 bytes. |
ShortLastRecord | S | If set to true, short reads are ignored on the last record of the file. In other words, the last record is processed even if the End of File (EOF) is reached before reading the end of the record. The default is false. |
StartOffset | S | If your source data file starts with characters that need to be excluded from the transformation, set the StartOffset option to specify at which byte of the file to begin. The default value is zero. The correct value may be determined by using the Hex Browser. For a list of the 256 standard and extended ASCII characters, search for "hex values" in the documentation. Note: This property is set in number of bytes, not characters. |
OccursPad | S | When using COBOL files, you may have fields of variable length. If so, you may specify how to fill the field with pads to a fixed length. The default is None. The following options are available: • None (which leaves the fields uneven) – Default • End of Record (which fills the remainder of the record with your specified pad character) • Within Group (which fills the field with your specified pad character) |
CodePage | ST | This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US. |
Property | S/T | Description |
MaxRecordLength | S | This specifies the maximum record length of the data. The default is 32700 bytes. |
ShortLastRecord | S | If set to true, short reads are ignored on the last record of the file. In other words, the last record is processed even if the End of File (EOF) is reached before reading the end of the record. The default is false. |
StartOffset | S | If your source data file starts with characters that need to be excluded from the transformation, set the StartOffset option to specify at which byte of the file to begin. The default value is zero. The correct value may be determined by using the Hex Browser. For a list of the 256 standard and extended ASCII characters, search for "hex values" in the documentation. Note: This property is set in number of bytes, not characters. |
OccursPad | S | When using COBOL files, you may have fields of variable length. If so, you may specify how to fill the field with pads to a fixed length. The default is None. The following options are available: • None (which leaves the fields uneven) – Default • End of Record (which fills the remainder of the record with your specified pad character) • Within Group (which fills the field with your specified pad character) |
Record Length Inclusive | ST | When true, this setting indicates that the record length indicator includes the bytes of the indicator itself. The default is false, meaning that the record length indicated does not include the bytes of the indicator itself. |
RLF MSB first | ST | This setting adjusts the byte order of the Record Length Field, also called the Record Descriptor Word (RDW). The default is true, which means the Most Significant Byte of the record length field is first. |
Word Align Record | ST | Tells the integration platform to align records on a word (16-bit) boundary when true, which is the default. |
CodePage | ST | This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US. |
Property | S/T | Description |
MaxRecordLength | S | This specifies the maximum record length of the data. The default is 32700 bytes. |
ShortLastRecord | S | If set to true, short reads are ignored on the last record of the file. In other words, the last record is processed even if the End of File (EOF) is reached before reading the end of the record. The default is false. |
StartOffset | S | If your source data file starts with characters that need to be excluded from the transformation, set the StartOffset option to specify at which byte of the file to begin. The default value is zero. The correct value may be determined by using the Hex Browser. For a list of the 256 standard and extended ASCII characters, search for "hex values" in the documentation. Note: This property is set in number of bytes, not characters. |
RecordSeparator | ST | This specifies what sort of character is used to mark the end of a record. The default record separator is carriage return-line feed. To use other characters for a record separator, click the RecordSeparator cell, click the arrow and select a record separator. Choices are carriage return-line feed (default), line feed, carriage return, line feed-carriage return, form feed, empty line and no record separator. |
OccursPad | S | When using COBOL files, you may have fields of variable length. If so, you may specify how to fill the field with pads to a fixed length. The default is None. The following options are available: • None (which leaves the fields uneven) – Default • End of Record (which fills the remainder of the record with your specified pad character) • Within Group (which fills the field with your specified pad character) |
CodePage | ST | This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US. |
Property | S/T | Description |
IgnoreMemoErr | ST | The following options determine how Visual dBASE memo files are handled: • Never - this is the default. This option causes the integration platform to look for and include any memo file fields when the source data file is read. • Errors - Selecting this option causes the integration platform to look for and include any memo file fields when a memo file is present. If present, the memo fields are included with the transformed data. • If the memo file (.DBT) is not in the same directory as the data file (.DBF), the memo file is ignored. This means that the memo fields are not included with the transformed data. • Always - Selecting this option causes the integration platform to ignore the memo file completely. This means that the memo fields are not included with the transformed data. |
CodePage | ST | This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US. |
Property Name | S/T | Description |
AttrFields | S | XML Attributes are considered as fields. The default is true. |
DoctypeRecsOnly | S | Build records that exist below the DOCTYPE (root). The default is false. If you want to define only the records that actually appear in the root, change this option to true. Otherwise, Map Editor defines all possible records, including those below the root. |
IgnoredAttributes | S | A list of attributes that must be ignored when determining file structure. The default is e-dtype a-dtype. |
IgnoreWhite | S | Ignores "ignorable" whitespace. The default is true. |
MaxQualifications | ST | Allows you to control how much recursion is allowed when using QualifiedRecordNames with nested objects. Default value is 0 to indicate no limit. |
QualifiedRecordNames | S | Qualifies record names with higher-level records. The default is false. Tip: Set this property to true to see the hierarchy of parent-child relationships of all record types, including different child record types with the same names. This property qualifies all the records with the hierarchical path from which the record is used. In other words, it concatenates the parent record names as it goes down the hierarchy, thereby creating unique record names. This allows you to get separate events for what is the same record, but under a different parent or set of parents. This is a source property only. However on the Target side, if you have a DTD, you can specify XML (DTD) Qualified Records in the Target Schema and select the DTD you want to use as a structure. |
RootDataElements | S | Reads all the data elements contained within the doctype element without creating records based on these elements. Note: When you set the RootDataElements property to true, the entire document is read into memory before any records are parsed. Sample document: <root> <data>Here is some data</data> <record> <data1>Here is some data</data1> <data2>Here is some data</data2> </record> </root> The preferred method is to read the data element as a record containing one field that is also named data. This way, the data can be read normally, without setting the RootDataElements property and without reading the entire document into memory. However, if you use a schema to read from an external DTD subset, the transformation XML schema may not be able to set the records up this way. In this case, setting the RootDataElements property causes the entire data set to be read into memory before it is parsed. This also allows the root record to contain a data field, which is populated with data. |
Schema | S | XML Schema that must be used. |
StripLeadingBlanks | S | For an XML source file, by default, Map Editor strips leading blanks in XML data. If you do not want to delete the leading blanks, select False. |
StripTrailingBlanks | S | For an XML source file, by default, Map Editor strips trailing blanks in XML data. If you do not want to delete the trailing blanks, select False. |
StyleSampleSize | S | Allows you to set the number of records (starting with record 1) that Map Editor analyzes to set a default width for each field in your source file. The default value for this option is 5000. You can change the value to any number between 1 and the total number of records in your source file. As the number gets larger, Map Editor requires more time to analyze the file, but it may be necessary to analyze every record to ensure no data is truncated. |
ElementRecords | S | All elements are considered as records. |
ByteOrder | T | Allows you to specify the byte order of Unicode (wide) characters. The options are: • Auto (default) - Determined by the architecture of your computer. • Little Endian- Generally used by Intel machines and DEC Alphas and places the least significant portion of a byte value in the left portion of the memory used to store the value. • Big Endian - Used by IBM 370 computers, Motorola microprocessors and most RISC-based systems and stores the values in the same order as the binary representation. |
DoctypeName | T | Doctype that Map Editor uses to create the target file. The default is recordset. |
DTDFile | T | Allows you to specify the name of the DTD file that Map Editor writes to or references when the target file is created. If this is left blank, the default file name is DOCNAME.DTD. |
Encoding | T | Allows you to select the type of encoding used with your source and target files. The default encoding is ISO-8859-1. Shift-JIS: This encoding is meaningful only to users with Japanese operating systems. |
Formatted | T | Select output with or without line breaks and indenting. If set to true (default), the output is written with the current line breaks and indenting. If set to false, the output is written with no line breaks or indenting in the body of the XML document. Tip: Large XML messages that include hierarchical formatting can greatly slow down near real-time processing. Use this property to write data strings without formatting to alleviate the formatting overhead issue. |
InternalSubset | T | Specify the internal DTD subset to write when referencing an external subset. To select an internal DTD, click the box and click once. Type the text of the internal DTD subset, without the '[' and ']' characters that encloses the internal subset in the DTD. |
ProcessingInstructions | T | Type a description of the processing instructions. These instructions are similar to the DTD declaration, since it instructs the XML parser about the methodology used to produce this XML instance. This is optional. These instructions are written after the XMLDecl (if it exists) and before the DTD file (if it exists). See the following example for the syntax. In the Processing Instructions example, Line 1 is the XMLDecl, Line 2 is the processing instructions and Line 3 is the DTD file: Example: ' With Processing Instructions?xml version="1.0" encoding="ISO-8859-1"? <processing instructions> !DOCTYPE PurchaseOrder SYSTEM "x:\xml\orders\filename.dtd" ' Without Processing Instructions ?xml version="1.0" encoding="ISO-8859-1"? !DOCTYPE PurchaseOrder SYSTEM "x:\xml\orders\filename.dtd" |
WriteDTD | T | Allows you to specify the type of DTD file to write when creating the target file. The available options are None, Internal, External, and Reference. The default is none. |
WriteEmpty | T | Indicates whether or not to write elements as empty fields. The default is true to write the elements as empty. Select False to suppress writing of elements as empty fields. |
WriteEmptyAttributes | T | Indicates whether or not to write attributes as empty fields. The default is true to write the attribute information in a tag. Select False to suppress writing the tag when it contains no data. |
WriteXMLDecl | T | The XMLDecl code lists the XML version number and the type of Encoding used in the XML file. To turn off writing the XMLDecl, select False. The default is true. |
RetainRecordOrder | T | The default is false. If set to true, record-type elements appear within their parent element in the order they were “put.” This has a couple of side-effects. When this property is true within a given element, all elements contained with a record data type appear after all elements that have any other data type. If this is not required, then the non-record elements must be transformed to record-type elements with only one field, using the same name as the record. This way, the order of all elements may be controlled. However, when this property is true, it is impossible to write an empty element of record data type. |
Footer | T | Allows providing text that will get written at the end of the document. |
UseEmptyTag | T | Specifies whether an empty element is written instead of a start element/end element tag pair. |
IsChildTextNode | T | Specifies whether to use a child node as text node if name of the field is the same as name of the record. If you have a record named R1, and it has fields R1 and R2, it specifies whether to write <R1>Text for R1 field <R2> Text for R2 field</R2> </R1> or <R1> <R1>Text for R1 field</R1> <R2>Test for R2 field</R2> </R1> |
Property | Type | ST | Use |
Batch Size | Number | S | Sets the number of records to be read at one time. A value of 0 means to read all. If a value greater than 0 is set, due to document structure constraints, more records may actually have to be read. Default is 1000. |
Namespace Prefixes | Boolean | S | Determines whether to include namespace prefixes in generated field names. Default is true. Use of namespace prefixes requires that the schemaLocation and noNamespaceSchemaLocation properties are not set. If either of those properties is set, then set this property to false. |
FlushFrequency | Number | T | Number of record inserts to buffer before sending a batch to the connector. Default is zero. If you are inserting many records, change the default to a higher value to improve performance. |
Batch Response | Filename | T | Sets the path name for a batch response file. Caution! Do not use this property. It is included only for backward compatibility. |
Formatted | Boolean | T | Sets whether the output should be formatted. If true, each element starts on a new line, with the hierarchy shown by indentation of two spaces per level. If false, output is written in the XML document body without line breaks or indentation. Default is true. |
Use Empty Tag | Boolean | T | For empty elements, use an empty tag or start or end a tag pair. If true, empty elements are written as an empty element as <element/>. If false, empty elements are written as a start element/end element pair <element></element>. Default is true. |
Write Empty Fields | Boolean | T | Write elements as empty fields. The default is true. If true, empty fields are written. Empty means they contain an empty string, are null, or are not set. If false, no elements are written for these fields. Default is true. |
Write Empty Attributes | Boolean | T | Write attributes as empty fields. The default is true. If true, empty attribute fields will be written as an attribute. Empty means they contain an empty string, are null, or are not set. If false, no attribute is written for these fields.Select False to suppress writing the tag when it contains no data. Default is true. |
HTTP Write Method | - | T | To write to an HTTP target, select POST or PUT. Default is POST. |
Write Namespaces | Boolean | T | Enable writing of namespace attributes or prefixes. Default is true. |
Namespace Map | Text | T | Enter the namespace mappings of the form pfx:namespace. Separate multiple values with newlines or spaces. |
Default Namespace | Text | T | Optional. Sets the default namespace for the xmlns attribute. |
Schema Location | Text | T | Optional. Sets the xsi:schemaLocation attribute on the root element. |
No Namespace Schema Location | Text | T | Optional. Sets the xsi:noNamespaceSchemaLocation attribute on the root element. |
Generate Prefixes | Boolean | T | Generate namespace prefixes or redefine the default namespace as needed. |
Prefer Type Substitution | Boolean | T | Use type substitution or element substitution for polymorphism if both are usable. |
Write XML Decl | Boolean | T | Write the first line of XML encoding declaration. Default is true. |