Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace Informix
Created by Guest
Created on Nov 2, 2019

Modernize dbexport/dbimport and control them from HQ

dbexport and dbimport are useful tools, very easy to use and straight forward. but as the database are growing exponentially, the tool is showing its limitations and a workaroud must be generally be  applied, which are kind of time consuming to write them.

Needed by Date Mar 31, 2020
  • Guest
    Dec 2, 2020

    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:

  • Guest
    Dec 19, 2019

    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.


  • Guest
    Nov 14, 2019

    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

    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
         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.