Modernize dbexport/dbimport and control them from HQ

All of this except control from InformixHQ, including the notes in other comments, can be accomplished by using myexport and myimport instead of dbexport and dbimport. You can download this package and the utils2_ak package on which it depends (both free and open source) from here:

www.askdbmgt.com/my-utilities

One more topic could be added here. When exporting, all language and codeset relevant variables should be noted in the script file, so that you don't have to speculate with which CLIENT_LOCALE, DBDATE, DBMONEY the export was created.

dbimport should warn if the current values differ.

regards
Andreas

10) export should unload tables with parallel jobs
      (export_unload temp table with all tables to unload, each job get a table out of temp
       table to unload - and deletes it out of temp table after unload. Each job is running until
       there are no rows in temp table.)
11) import should load tables with parallel jobs
      (import_load temp table with all tables to load, each job get a table out of temp
       table to load - and deletes it out of temp table after load. Each job is running until
       there are no rows in temp table.)
12) import should create indexes parallel ..
13) compressed unload via named pipe.. / uncompressed load via named pipe
14) external table FORMAT 'INFORMIX' - is faster, but don't work with coltype
     ==(11,12,19,20,21,22,23,41)

to 6): ALTER TABLE .. TYPE (RAW) during import does only works if there are no
      indexes/constraints inside table definition. So a workaround for this problem could
      be to run a ALTER TABLE ... DROP CONSTRAINT PRIMARY KEY, CREATE UNIQUE
     INDEX ... ; ALTER TABLE ... ADD CONSTRAINT PRIMARY KEY before export.
to 10...12): extend sizes should be set correct to size of table/index before loading table/
     creating indexes.

Cheers,
Markus