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

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Future consideration
Created by Guest
Created on Feb 16, 2023

The column length is too short in some Omegamon tables

We use JPA to generate Dynamic SQL in Db2 z/OS. The application ID i sent in the field ClientInfo which helps us to identify the processing. The application ID is often quite long.

Some Omegamon tables have columns that contain data from ClientInfo.   

In SMF-records and in the Omegamon tables xxxx_GENERAL and xxxx_PROGRAM the information is CHAR(255). In the tables  xxxx_DEADLCK and xxxx_TIMEOUT the columns BLOCK_TRANSACT, WAIT_TRANSACT and TRX_NAME are just CHAR(32). To help us identify the causer in locking conflicts these columns have to be the same length as in SMF records.