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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Mar 19, 2019

Allow shorter audit value columns

The audit columns defined as GENERATED ALWAYS AS USER, SESSION_USER or CURRENT CLIENT_USERID require the column to be either 18, 128 or 255 bytes.

While this is maybe a theoretical limit it makes no sense in 99.999% of the cases as usernames on IBM i can only be 10 characters and on other platforms no-one is using such long user names (maybe 20 characters max).

Using ALLOCATE limits the overhead on the table, but not on journals.


Use Case:

It would therefore be logical that the length of those fields is not enforced but that I can choose myself which length it should be (and DB2 for i should just truncate - with no error - the value if it is ever longer)


Idea priority Medium
  • Guest
    Reply
    |
    Jan 16, 2021

    IBM does not intend to provide a solution to this request at this time, so it is being closed.

    While we agree that this is a valid request, we do not currently plan to implement it because there is a long list of higher priority requirements.

    The SESSION_USER and USER special registers are always the same value, so consider using USER. CURRENT CLIENT_USERID is one of the special registers that can be modified by an application to contain any application-provided value. Allowing a shorter column length for this auditing value could be expected to lose meaningful data.