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 Future consideration
Workspace IBM i
Categories Languages - RPG
Created by Guest
Created on Nov 17, 2016

Option for EXTNAME/LIKEREC(*NULL) to create SQL-type int(5) indicator subfields

LIKEDS is used for creating parallel data structures -- i.e., data structures that have the same list of subfields as another data structure. But, sometimes it is useful to have the same list of subfields but with a different set of data definitions for those subfields.

I can think of several cases like that. But the case that I encounter most frequently is an SQL Indicator array that is overlaid with a data structure providing named indicators as subfields. Having to manually maintain the list of subfields in this data structure every time the associated table/view record format changes is both tedious and error-prone.

It would be very helpful if RPG could/would auto-generate such a parallel data structure in much the same way that it currently auto-generates the data structure for an external table/view record format. To do this requires a simple extension to the LIKEDS keyword -- as shown in the Use Case below.


Use Case:

// number of columns in SQL row
dcl-c IMLFCMP_VCol1 17;
dcl-c IMLFCMP_VCol2 30;

// data structures for SQL column data
dcl-ds IMLFCMP_View1 extname('IMLFCMPV01') qualified inz end-ds;
dcl-ds IMLFCMP_View2 extname('IMLFCMPV02') qualified inz end-ds;

// SQL indicator array with overlay of named indicators
dcl-s IMLFCMP_Ary like(NULL_VALUE) dim(IMLFCMP_VCol2) inz;
dcl-s IMLFCMP_Ptr like(pointer_t) inz(%addr(IMLFCMP_Ary));
dcl-ds IMLFCMP_Ind likeds(IMLFCMP_View2: 'INT(5:0)')
based(IMLFCMP_Ptr) qualified;


Idea priority High
  • Guest
    Reply
    |
    Apr 27, 2020

    This request is still a candidate to be an enhancement for the RPG compiler.

  • Guest
    Reply
    |
    Feb 27, 2018

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. Although one can make one's own array as a work-around, that is clumsy. Embedded SQL should be supported in the same way as native RPG.

    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 www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Reply
    |
    Mar 30, 2017

    IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it. IBM will use votes and comments from others in the community to help prioritize this request.

  • Guest
    Reply
    |
    Feb 10, 2017

    IBM has received the requirement and is evaluating it. IBM will provide a response after evaluation is complete.

  • Guest
    Reply
    |
    Jan 31, 2017

    IBM has modified some of the information in this request. Specifically, with the Submitter's approval, the Headline is being changed. Previous Headline was "Extension to LIKEDS processing". New headline is "Option for EXTNAME/LIKEREC(*NULL) to create SQL-type int(5) indicator subfields". Please contact us if you have any questions.

  • Guest
    Reply
    |
    Jan 27, 2017

    IBM needs more information to further assess your Request for Enhancement.

    It is now possible for IBM to change the title of an RFE, after getting agreement from the submitter. This RFE currently only has two votes; I think a more meaningful title will probably attract more votes. If the underlying requirement is to have a data structure with SQL-type int(5) indicators, similar to the current *NULL support in 7.3 that creates a data structure with RPG-type indicators, then we suggest the title for this RFE be changed to "Option for EXTNAME/LIKEREC(*NULL) to create SQL-type int(5) indicator subfields"

    Dave, if you agree with the title change, or would like to have an alternate new title, please add a response saying so.

  • Guest
    Reply
    |
    Nov 18, 2016

    Assuming that the basic intention behind this RFE is to make it easier to define null indicator structures then it really needs to be changed. I can't vote for this as-is - I just don't like the proposed implementation. I do like Barbara's suggestion and would vote for that because (in part) as a logical extension of existing functionality it is easier to remember and undoubtedly easier (read cheaper and therefore more likely to happen) for IBM to implement.

  • Guest
    Reply
    |
    Nov 17, 2016

    Dave, it's unlikely that this request would be implemented as a general enhancement to LIKEDS.

    If the underlying requirement is really to make it easier to work with null indicators in RPG, I think it would be better if you changed the title to something about RPG supporting the SQL style of null indicators for EXTNAME(*NULL). You can change the RFE title as long as it's within 24 hours of creation.

    In case you're not aware of it, a 7.3 enhancement added support for EXTNAME(*NULL) and LIKEREC(*NULL), which gives a data structure with indicator subfields rather than the data type of the field in the file. A further enhancement that I think would satisfy your underlying requirement would be to support something like EXTNAME(*SQLNULL), which would give int(5) subfields. Entailed in that enhancement would be RPG support for the integer type of null indicator for its NULLIND support (where you can associate a *NULL indicator DS as the %NULLINDs for an externally-described DS.)

  • Guest
    Reply
    |
    Nov 17, 2016

    Dave, it's unlikely that this request would be implemented as a general enhancement to LIKEDS.

    If the underlying requirement is really to make it easier to work with null indicators in RPG, I think it would be better if you changed the title to something about RPG supporting the SQL style of null indicators for EXTNAME(*NULL). You can change the RFE title as long as it's within 24 hours of creation.

    In case you're not aware of it, a 7.3 enhancement added support for EXTNAME(*NULL) and LIKEREC(*NULL), which gives a data structure with indicator subfields rather than the data type of the field in the file. A further enhancement that I think would satisfy your underlying requirement would be to support something like EXTNAME(*SQLNULL), which would give int(5) subfields. Entailed in that enhancement would be RPG support for the integer type of null indicator for its NULLIND support (where you can associate a *NULL indicator DS as the %NULLINDs for an externally-described DS.)

4 MERGED

Add a NULL (nullable) Attribute and related built-ins to Fields in RPG IV

Merged
The pervasive use of SQL in RPG IV along with the habitual use of NULL-capable fields justifies adding a ALLOW(*NULL) keyword to stand-alone fields, data structure subfiles, as well as parameters. It would be used on things like the SQL FETCH clau...
12 months ago in IBM i / Languages - RPG 1 Future consideration