User Guide > Map Connectors > Source and Target Map Connectors > Binary
Was this helpful?
Binary
The Binary connector can be used to read or write almost any fixed-length single record type file. Whether the data is straight ASCII, some combination of EBCDIC and packed data, flat COBOL files, C, or BASIC files, you can define the record structure and transform the data to another format or application.
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 the file can be read. When writing out 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 Binary 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 as an ASCII character.
3. Example: If the separator is a line feed, enter LF
4. To use a hex value instead, go to step 3.
5. Enter a backslash, an "x", and the hex value for the separator.
6. Example: If the separator is a line feed, enter \x0a.
For a list of the 256 standard and extended ASCII characters, search for "hex values" in the help.
Connector Parts
Connector parts are the fields you configure to connect with a data source or target. The fields that are available depend on the connector you select.
For a list of all parts for source connectors, see Specifying Source Connector, Parts, and Properties.
For a list of all parts for target connectors, see Specifying Target Connector, Parts, and Properties.
Property Options
Note:  If you have EBCDIC source data, it is necessary to set the proper EBCDIC code page before setting the field widths.
You can specify the following source (S) and target (T) properties:
Property
S/T
Description
CodePage
S/T
This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US.
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 by selecting one of the following:
• None (the default) – leaves the fields uneven.
• End of Record – fills the remainder of the record with your specified pad character.
• Within Group – fills the field with your specified pad character.
PageSize
S/T
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
S/T
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 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.
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.
Note
This property is set in number of bytes, not characters.
 
 
Supported Data Types
The following data types are supported:
• 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: 06/30/2025