Eloquence MPE migration utilities --------------------------------- Revision: B.07.10 beta (2005-03-22) This archive provides an updated version of the Eloquence MPE data migration tools. The major difference is that dbexport may now be used to create bexp files in addition to the text based export files. To create bexp files dbexport needs to run in privileged mode and must be copied to a privileged group after compiling. Also the binary capabilities must be changed with linkedit. At this point, only source files are available. Building was only tested with the HP C compiler. Limitations: - No support for Business Basic decimals - Export files are limited in size to 2GB - Binary export mode includes the IMAGE record number and chain pointers along with a binary representation of the record. Any broken chains will show up in Eloquence. How to compile -------------- Transfer the files to MPE, start a POSIX shell and run make. As a result the file DBEXPORT and DBINFO are built. How to install -------------- If the new bexp format is not required the executables may be installed in an arbitrary location. To use the new bexp format, the files should be installed in a privilged group and the DBEXPORT capbilities need to be changed as shown below: :linkedit altprog DBEXPORT; cap = ia,ba,pm exit This adds the PM capability to DBEXPORT. How to use the binary export mode --------------------------------- The binary export mode is used when the -B (upper case B) command line option is specified. The new binary export mode creates a separate file for each dataset (unless it has zero entries). DBEXPORT uses the naming convention DBNAME.999.exb for each binary export file. The binary export file includes a header to identify the data in the file and for each record the original record number and the chain pointers (besides the sysnonym chain information for a master set). This information may then be used by the Eloquence bimport to efficiently import the database into Eloquence, retaining the chain order and record number for any detail set. How to use bimport on Eloquence ------------------------------- The new bimport function allows to efficiently import data from TurboIMAGE while retaining the chain information. For a detail set the record number is also retained. While undocumented, the bimport function is included for testing purposes in the most recent Eloquence B.07.00 eloqdb patches (PE70-0501070 or newer) for the HP-UX platform. Currently, bimport is not a convential utility program but builtin the server process and run with the dbctl utility. dbctl bimport [options] database set bexp_file This first erases the specified data set and then processes the specified import file. As the bimnary import files are directly accessed by the eloqdb6 server process the files must be readable by the user that is configured for the eloqdb6 and must reside on the same system. The following options are supported with bimport: /v - Display additional information. Specifying the option /v twice (/v /v) causes the import progress to be output to stderr for every 10,000 records. /a - In case more than one bexp file is needed to import a data set this flag is specified with any subsequent bexp file. /n - This file must be specified if additional bexp files exist for this data set. As the current MPE dbexport only creates a single binary export file for each data set, the options /a and /n should not be used. Please note that PE70-0501070 has a small bug bug that causes a hang when the bimport /v option is used and EnableIPC=0 is configured. An example script (bimport.sh) is provided that may be used to automatically import a single database.