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 Future consideration
Workspace IBM i
Categories Web Serving
Created by Guest
Created on Apr 16, 2018

More flexible list

When defining a Web Service using IWS it's only possible to limit the size of the returned list by selecting a return parameter that is placed as a first level parameter field when using the "Count" feature or by using the hard coded feature "Detect length fields".

Suggestion: Make it possible to also select the "Count"/Returned rows from a sub field in a parameter data structure.

This RFE was earlier defined as a CEAC Request with ID AD0260.

Use Case:

A big customer of mine have the "returned rows" field placed as a subfield in a parameter structure/DS together with "EOF indication" of the list. This makes it impossible to only return rows containing data in the SOAP XML or REST JSON interface without changing the API interface.

As the API interfaces can't be changed the effect is that the maximum size of the structs/lists are always returned with or without data. Customers think that this is odd...

Idea priority High
  • Guest
    May 9, 2018

    I have tried this more now and see that i'ts possible to add a _LENGHT field as a parameter in the RPG program and use the Detect feature.
    You're correct that this doesn't effect the the Web Service interface but the RPG API programs are also used via remote call using JTOpen. That for high speed integration. This means that the RPG API program can't be changed with a new parameter.

    Another question is why the COUNT and _LENGHT fields needs to be INTEGER and not PACKED or ZONED? Isn't a numerical field good enough?

    At the same time I would like to thank the team for a great product and support!


  • Guest
    Apr 16, 2018

    I know all about the Detect length fields and have tried it. It changes the WSDL and Swagger files ie the API interface and doesn't meet my customers need. If you look how you have implemented the Browse feature when naming the Program or Service Program in the IWS wizard, you see that you have supported how to make it possible to go deeper in a structure to select something.

  • Guest
    Apr 16, 2018

    As indicated, the support for Detect length fields should meet your needs. To read more about it, please read the section titled "Support nested output arrays" in the article: "Integrated web services server for IBM i updates" at the following URL:

    Adding the length fields does not change what the customer sees in swagger document or WSDL document. Yes, you may need to change or add a thin layer if you want to specify length fields.

    There is no way to allow users to select arbitrary fields in structures for array length fields. It would make the GUI interface much more complicated.