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 Submitted
Workspace IBM i
Categories Languages - RPG
Created by Guest
Created on Jul 31, 2026

Provide a DCL-DEFN and END-DEFN block to define stand-alone fields without DCL-S

When declaring many fields in RPG IV, today we have to code DCL-S on every field name.It would be great to be able to do something similar to what we do with DCL-DS / END-DS and have a declarative block or "definition" block to define regular fields in this context. The idea is that we would have a "DCL-DEFN" and "END-DEFN" block and all entities between them are declare as if they each had their own "DCL-S" prefix. Note due to formatting challenges in this editor, I've also pasted in the code example as a .PNG image.dcl-defn; seqnbr int(10); custNbr packed(7 : 0); custname varchar(30); notes varchar(50); YTD_Sales packed(9 : 2); last_sales_date date; end-defn;

Idea priority Medium
  • Guest
    Aug 19, 2026

    Thank you for taking the time to submit this IBM Idea and share your feedback with IBM and the broader IBM i community.

    The CAAC has reviewed this Idea and, after careful consideration, does not recommend that IBM move forward with the request in its current form at this time.

    Reason: The CAAC did not identify sufficient community-wide value in introducing an additional syntax for declaring stand-alone fields. The existing DCL-S syntax clearly identifies each field as a stand-alone variable. A DCL-DEFN and END-DEFN block could be mistaken for a data structure, potentially making RPG code less immediately clear for both new developers and those maintaining unfamiliar code.

    Although the CAAC is not recommending implementation of this request, Ideas such as this help IBM and the CAAC better understand the needs and priorities of the IBM i community. We appreciate your contribution and encourage you to continue submitting IBM Ideas and sharing your feedback.

    Background: The COMMON Americas Advisory Council (CAAC) includes members with a broad range of experience working with small and medium-sized IBM i clients. The CAAC works with IBM i development to help assess the potential value and impact of individual IBM Ideas on the broader IBM i community.

    For more information on the CAAC, visit: https://www.common.org/common-americas-advisory-council/

    Brandon Pederson - CAAC Program Manager

  • Guest
    Aug 17, 2026

    Yes, it is like a non-QUALIFIED data structure, expect each variable is a stand-alone field instead of part of a data structure.

  • Guest
    Aug 6, 2026

    Its like declare a no-name data structure without qualified keyword