Skip to Main Content
IBM Power Ideas Portal

This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

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.

Status Delivered
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Apr 19, 2023

Provide buffer length of LOB columns in SYSCOLUMNS2 view

When processing I/U/D entries from a journal using the DISPLAY_JOURNAL we need to "map" the entry specific data over the record layout. The amount of space occupied by a LOB column varies; depending upon where in the record the column starts. So two identically defined LOB columns can take up a different amount of space in the record layout.

It would be extremely useful if SYSCOLUMNS2 would return the actual amount of space occupied by LOB columns in the record, so that the remaining columns can be mapped correctly.

Numeric columns specify the length occupied plus the numeric precision / scale. A similar approach should be considered for LOB columns.

Idea priority Urgent
  • Guest
    Nov 16, 2023
    This enhancement was delivered in November 2023 with IBM i 7.5 PTF Group level 5 and IBM i 7.4 PTF Group level 26.


    You can read about it on the fact page here:
    And in IBM Documentation here:

    Db2 for i development team
    IBM Power Systems Development
  • Admin
    Carmelita Ruvalcaba Cevallos
    May 30, 2023

    The CAAC has reviewed this IBM Idea and recommends that IBM view this as a high priority Idea that is important to be addressed.

    This will add benefit to the community.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual IBM Ideas on the broader IBM i community and has therefore reviewed your Idea.

    For more information about CAAC, see

    Carmelita Ruvalcaba- CAAC Program Manager

  • Guest
    Apr 21, 2023

    *why bother bringing it in

  • Guest
    Apr 21, 2023

    This is a curious issue. I'm thinking why a LOB LOCATOR isn't "just" returned in the record buffer so that it is 100% consistent. Since LOB data is stored "elsewhere" anyway, why both bringing it in unless the developer requests it to be brought it. A LOB LOCATOR would accompilsh that so we could "just" say "Okay I need the LOB data, let use the locator to get that. Seems infinitly easier to me. But yes, something for consistency is sorely needed.

  • Guest
    Apr 19, 2023
    IBM will use this Idea as input to planning, but no commitment is made or implied. This Idea will be updated in the future if IBM implements it.