User Guide > Map Connectors > Source and Target Map Connectors > Binary (International)
Was this helpful?
Binary (International)
The Binary (International) connector can be used to read or write almost any fixed-length data file. Whether the data is straight ASCII, some combination of EBCDIC and packed data, C, or BASIC files, the integration platform allows you to define the record structure and transform the data to another format or application.
Note:  This connector is not a Unicode-enabled connector. Because of this, to get the desired results, you must set your computer for your particular language type. For example, if you have traditional Chinese or Japanese EBCDIC data, you must set your computer system locale to recognize traditional Chinese or Japanese character sets.
Because the integration platform is not a communication package, data that resides on a mainframe or mini-computer must first be downloaded to a local or network drive before it can read the file. When writing a file to be used in an application on another platform, you write the file to a local or network drive. Then use a communication package to move that data file to the mainframe or mini system.
Multiple Record Types Possible
Binary files can contain multiple structured schemas. If your source file has multiple structured schemas, you can find information by searching in the help for "multiple record types."
Connector-Specific Notes
This connector does not support truncation error trapping. If the target field size is too small for the data written to it, the offending record may be skipped or incomplete data may be written to the target. The transformation does not stop due to a truncation error.
If the alternate field or record separator is not listed
1. Highlight the default separator.
2. Enter the separator in binary or hex.
• ASCII: Enter the appropriate character code.
If the separator is a line feed, enter LF.
• Hex: Enter a backslash, an "x", and the hex value for the separator.
If the separator is a line feed, enter \x0a.
Binary (International) Unicode Support
The Binary (International) connector is not a Unicode connector, but depending on your operating system it might support double-byte encoding. For example, if you are running an English operating system, you cannot process Japanese data.
If you select Unicode encoding and you need to set up a record separator, set the RecordSeparator property to None. Then, create an additional field to hold the Unicode bytes.
Supported Binary (International) Encoding
Name
CP930
EBCDIC host mixed Katakana-Kanji
CP933
EBCDIC mixed Korea
CP935
IBM EBCDIC Simplified Chinese, Combined (836 + 837)
CP937
EBCDIC Traditional Chinese
CP939
EBCDIC mixed Latin-Kanji
DEC
Digital VAX and Unix, DEC Kanji code
IBM78+EBCDIC
IBM mainframe and AS/400, 1978 Kanji and non-kana support
IBM78+EBCDIK
IBM mainframe and AS/400, 1978 Kanji and half-width kana
IBM83+EBCDIC
IBM mainframe and AS/400, 1983 Kanji and non-kana support
IBM83+EBCDIK
IBM mainframe and AS/400, 1983 Kanji and half-width kana
IBM937+EBCDIC
Traditional Chinese IBM mainframe and AS/400
ISO-2022-CN
Chinese ISO-2022
ISO-2022-CN-EXT
Chinese ISO-2022-EXT
ISO-2022-JP
Japanese ISO-2022
ISO-2022-JP-1
Japanese ISO-2022-1
ISO-2022-JP-2
Japanese ISO-2022-2
ISO-2022-KR
Korean ISO-2022
JEF78+EBCDIC
Fujitsu FACOM, 1978 Kanji and non-kana support
JEF78+EBCDIK
Fujitsu FACOM, 1978 Kanji and half-width kana
JEF83+EBCDIC
Fujitsu FACOM, 1983 Kanji and non-kana support
JEF83+EBCDIK
Fujitsu FACOM, 1983 Kanji and half-width kana
JIS78
Japanese Industrial Standard 1978
JIS83
Japanese Industrial Standard 1983
KEIS78+EBCDIC
Hitachi HITACH, 1978 Kanji and non-kana support
KEIS78+EBCDIK
Hitachi HITACH, 1978 Kanji and half-width kana
KEIS83+EBCDIC
Hitachi HITACH, 1983 Kanji and non-kana support
KEIS83+EBCDIK
Hitachi HITACH, 1983 Kanji and half-width kana
MELCOM
Mitsubishi MELCOM, MELCOM Kanji
NEC JIPS-E
NEC ACOS, NEC JIPS-E code
NEC JIPS-E (Int)
NEC ACOS, NEC JIPS-E internal code
NEC JIPS-J
NEC ACOS, NEC JIPS-J
NEC JIPS-J (Int)
NEC ACOS, NEC JIPS-J internal code
Unisys LETS-J
Unisys UNIVAC, UNIVAC LETS-J Kanji
Property Options
You can set the following source (S) and target (T) properties.
Property
S/T
Description
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)
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.
Note:  This property is set in number of bytes, not characters.
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.
Encoding
ST
Select the type of encoding used with your Binary files. The default encoding is OEM. To change the encoding to a different selection, click the arrow and select an encoding from the list. Available options are OEM (default), Shift-JIS, Unisys LETS-J, UCS-2, UTF-8, UTF-16, and US ASCII.
Page Size
ST
When data records are arranged in blocks and the last record in each block is padded to the end of the block, it is necessary to set Page Size. This causes the pad characters to be stripped from the file during the data transfer. To set page size, click Page Size, highlight the default value (zero), and type the correct page size value for your data.
RecordSeparator
ST
When a COBOL file is your source connector and you are using a 01 copybook to define the fields, you might have a record separator at the end of each record. If so, you may specify the record separator as None, which causes the map to ignore the record separator when it reads the source data. The default is None.
The separators are carriage return-line feed (CR-LF), line feed (LF), carriage return (CR), line feed-carriage return (LF-CR), form feed (FF), Empty Line, and none.
When writing out a binary file, you may want to place a record separator at the end of each record (similar to a Fixed ASCII record separator). You may select a record separator from the list, or highlight the current value and type your own.
Supported Data Types
The following data types are available:
• 16-bit binary
• 16-bit logical
• 24-bit binary
• 32-bit binary
• 32-bit IEEE floating-point
• 32-bit TEC binary
• 32-bit VAX floating-point
• 64-bit binary
• 64-bit IEEE floating point
• 64-bit VAX floating-point
• 8-bit binary
• 80-bit Intel floating-point
• AccPac 41-bit binary
• BCD
• Binary
• Boolean
• Btrieve date
• Btrieve time
• Column binary alpha-numeric
• Column binary multi-punch
• Column binary numeric
• Comp
• Comp-1
• Comp-2
• Comp-3
• Comp-5
• Comp-6
• Comp-X
• Complex
• Cray floating-point
• Date
• DateTime
• dBASE Numeric
• Display
• Display Boolean
• Display Date
• Display Date/Time
• Display justified
• Display sign leading
• Display sign leading separate
• Display sign trailing
• Display sign trailing separate
• Display Time
• Magic PC Date
• Magic PC Extended
• Magic PC Number
• Magic PC Real
• Magic PC Time
• Microsoft BASIC double
• Microsoft BASIC float
• Name
• Null-terminated C string
• Packed decimal
• Pascal 48-bit real
• Pascal string (1 byte)
• Pascal string (2 bytes)
• Sales Ally date
• Sales Ally time-1
• Text
• Time
• Time (minutes past midnight)
• Union
• Variable length IBM float
• Zoned decimal
Last modified date: 02/01/2024