Skip to Main Content
IBM Power Ideas Portal
Hide about this 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.

Provide a smart LIKE keyword that works with any target type (vs LIKE and LIKEDS)

See this idea on ideas.ibm.com

Today when we write code, we use the LIKEDS (mostly) to declare a data structure "like" another.

When a field is declared and should be "like" another existing field, we use the LIKE keyword.

Please provide a new keyword that can be used in either context so we can simply say "LIKE(vartemplate)" instead of having to determine if the referred variable is a data structure or a field.

Why? Because when generating code or copying code, we shouldn't have the extra burden of figuring out if the referenced variable is a structure or a field.

I suggest a new keyword, let's call it TYPE, that would do what I'm asking. Here's an example:

  dcl-s size_t uns(10);
  dcl-s ptr  pointer;
   dcl-ds Qdb_Mbrd0100_T  Qualified Inz TEMPLATE; 
   Bytes_Returned INT(10);                      
   Bytes_Available INT(10);                     
   Db_File_Name CHAR(10);                       
   Db_File_Lib CHAR(10);                        
   Member_Name CHAR(10);                        
   File_Attr CHAR(10);                          
   Src_Type CHAR(10);                           
   Crt_Date CHAR(13);                           
   Change_Date CHAR(13);                        
   Text_Desc CHAR(50);                          
   Src_File CHAR(1);                            
 end-ds;  // Qdb_Mbrd0100_T     
 
 dcl-s rtnLen type(size_t);
 dcl-s pMbrD  type(ptr);
 dcl-ds mbrDesc type( Qdb_Mbrd0100_T );
 dcl-s length type(*INT);
 dcl-s smallSize type(*int2);

 

The definitions of the fields RTNLEN, PMBRD, and MBRDESC are all based on other fields.

There could also be pre-defined types, to make things in routines consistent. For example *INT4, *INT2, *UINT2, *UINT4, etc. I suppose if TYPE(*CHAR) is specified, then LEN(nn) would be required to.                                      

Idea priority High