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 Core OS
Created by Guest
Created on Oct 20, 2017

increase user space size

The maximum size of an user space object is 16, 776, 704 bytes. This is no longer sufficient. If a library contains more than about 25.000 objects I can not dump all object information (QUSROBJD using OBJD0300) into the user space. Please increase the size from 16MB to 1GB.

Use Case:

Run QUSROBJD with format OBJD0300 against library QSYS. This will fail. I know there are ways around this with extra coding but I think 16MB is simply too small of the year 2017.

Idea priority High
  • Guest
    May 30, 2019

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

    For the API used in your example, QUSROBJD, perhaps a work-around would be to subset the data requested by object type. Another possible method for retrieving this information would be to use the OBJECT_STATISTICS table function.

  • Guest
    Feb 13, 2018

    The CAAC has reviewed this requirement and recommends that IBM not implement this request. There are work-arounds that can be used, so IBM should not increase the max size of a user space.

    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 RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see

    For more details about CAAC's role with RFEs, see

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Nov 29, 2017

    It is unlikely that we would "increase the size" of a user space. User spaces serve a purpose, but there are other storage methods available to handle amounts of data larger than 16Mb. APIs that return enough data to go over the 16Mb limit usually can be circumvented by requesting a different subset of data. When that is not possible (or not desirable) another method should be implemented by the API.

    Some API's which can return a large amount of data already use other methods to return that data. For example, QUSLJOB returns data into a user space, but it has an optional "continuation handle" to keep track of where it left off so the API can be called multiple times to return all the data. QGYOLMSG makes use of a byte stream file to return up to 2Gb of data.

  • Guest
    Oct 21, 2017

    Keeping the 16MB limit on user spaces is not the worst thing if there is a good workaround (as already suggested). Returning a reference to any additional userspaces would be a nice option.

  • Guest
    Oct 20, 2017

    There was a 3rd party solution to this by one of the people who wrote the original user space code. It worked by using exception trapping to auto-create additional user spaces when the current one hit the limit. Earlier attempts to get ibm to increase the size limit have been rejected because they didn't want to chance breaking the SPACE code since its use is pervasive in the system. My recommendation would be to request a modern alternative to auto-size user spaces. Perhaps one that uses the C language memmap function with IFS stream files.