Endian Migration
Convert Between Big, Little, and BOM - Regardless of Platform
Challenges
There is an inherent data compatibility problem between different endian architectures.
Binary numerics and multi-byte character data from “big endian” computers, like the mainframe, do not process correctly on “little endian” computers, like a Windows PC, and vice versa.
Different CPU architectures impose different byte orders on resident data. Incompatibilities in data recognition and processing can result.
Solutions
IRI offers endian designation and migration functionality in its software to process data from, or convert data to, big and little endian architectures.
IRI's ability to maintain and change the endianness of data at global, source (e.g. file) and field level means that data sources at these levels can be correctly processed on big, little, or bi-endian hardware. This facilitates off-loading of work from busy or more expensive systems to computers with more capacity but different endianness.
Field-level endian control facilitates the movement of data into and out of files and databases during data integration operations. Output big and little endian data to one or more targets simultaneously. Avoid the need for remediation processes, data redundancy, and synchronization.
The IRI Voracity data management platform, or these separately available constituent products, manage the endian issue in efficient, meaningful ways:
|
Acquires, transforms, and targets data as big or little endian, regardless of the endianness of the execution platform. |
|
|
Converts the byte order of files and fields to migrate data across platforms. |
|
|
Acquires, protects, and targets data as big or little endian, regardless of the endianness of the execution platform. |
|
|
Generates test data - files and fields – with the endianness required for each. |
