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 Not under consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Aug 4, 2018

Increase VARCHAR() Scaler to 65KB, 16MB or 2GB

Currently SQL VARCHAR() scalar function under DB2 for i supports lengths of up to 32k or 32k-1 w/Nullable values. HLL on IBM i support 64k Varchar column/fields as well as 16MB Varchar lengths. Other Platforms (Microsoft) also support much longer lengths (2Gb).

Use Case:

Using a high-level Language such as RPG IV, developers have the ability to retrieve data from Web sources, such as Watson/IBM Cloud and store that information. While fixed-length fields support very long data results, the SQL VARCHAR function and column attribute supports only 32k. This length is "old" and should be increased to at least 64k but I would prefer 16MB or even 2GB to be compatible with other platforms.

Idea priority Medium
  • Guest
    Jun 28, 2020

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

    As mentioned in prior updates, the structure of a VARCHAR data type in host languages and internally is a 2-byte binary length followed by the data. The VARCHAR scalar function has the same length limitation since the result data type is VARCHAR. To work with longer character data, the CLOB function resulting in a CLOB data type must be used. A CLOB can handle all the lengths supported by VARCHAR, so it is the preferred data type for any situation where more than 32K might be needed.

  • Guest
    May 9, 2019

    If you want to go beyond approximately 32K, you must use the CLOB scalar function because the result is a CLOB not a VARCHAR.
    You can use the CLOB function for must smaller values as well.