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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Created by Guest
Created on Aug 14, 2020

Improvement in the check for high serial values

I'm trying to check if a serial value has reached its upper limit. I noticed the following unpleasant behaviour.

In the sysmaster tables sysptnhdr and sysactptnhdr the currently used serial values are in three fields for the datatypes serial, serial8 and bigserial.

If my serial approaches the upper limit for integer data types, the easiest way is to change it to a serial8 or bigserial.

During the alter table, the current value from serial is now copied into the column of the new type. Unfortunately the value of serial is not reset to 0 or NULL.

This means that a value check still reports a dangerously high serial value, even though the table no longer has this data type.

Since you can have both types serial and serial8/BigSerial in a table in parallel, you must now also check the syscolumns of the affected database to suppress this message.

At least for databases with non-english locale this is even more difficult, because you cannot access directly from sysadmin or sysmaster.

My suggestion is that only the field of the data type that is used is filled with the current serial value and the others are reset to 0 or NULL.

A repro for this behaviour can be found in the support case TS002868693.

Needed by Date Sep 1, 2020
  • Admin
    Beate Porst
    Sep 11, 2020

    ok, closing this one

  • Guest
    Aug 17, 2020

    Sorry, the platform must be Informix -> Informix-Server

    I duplicated this RFE to INFX-I-383