Converts a database file from one endian format to the other (BIG to LITTLE or LITTLE to BIG). The format of the MUPIP ENDIANCVT command is:
mupip endiancvt [-outdb=<outdb-file>] -ov[erride] <db-file>
<db-file> is the source database for endian conversion. By default ENDIANCVT converts <db-file> in place.
outdb writes the converted output to <outdb-file>. In this case, ENDIANCVT does not modify the source database <db-file>.
ENDIANCVT produces a <outdb-file>of exactly the same size as <db-file>.
![[Important]](images/important.jpg)
Users must ensure adequate storage for <outdb-file> to complete the endian conversion successfully.
ENDIANCVT requires standalone access to the database.
GT.M displays a confirmation request with the “from” and “to” endian formats to perform the conversion. Conversion begins only upon receiving positive confirmation, which is a case insensitive "yes".
In a multi-site replication configuration, the receiver server automatically detects the endian format of an incoming replication stream and converts it into the native endian format. See Database Replication chapter for more information.
![[Note]](images/note.jpg) | |
GT.M on a big endian platform can convert a little endian database into big endian and vice versa; as can GT.M on a little endian platform. GT.M (run-time and utilities other than MUPIP ENDIANCVT) on a given endian platform opens and processes only those databases that are in the same endian format. An attempt to open a database of a format other than the native endian format produces an error. |