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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
We have developed a build system for native ILE code that we are preparing to release as open source. When coupled with a source control product like Git and bug tracking software like Trac (or Jira), it should provide a free (or nearly free) change management system for developing standard RPG, C, CL, etc. code and objects.
To work, some GNU tools are required to be installed in PASE: Awk, Grep, Make, and Sed. To date, only older, non-GNU versions exist in PASE.
We have installed the GNU tools on our system from the AIX packages on the perzl.org site, but it is a complicated process to do so, and the tools are not as recent as could be. For any sort of widespread adoption of this build system, there will need to be an easier way to get these tools onto an IBM i. If PASE shipped with GNU versions, that would be terrific, but including them in the 5733OPS product would also be great, as 5733OPS needs to be installed for this build system to work, anyway.
Multiple developers are developing and maintaining native IBM i software. Code is added, modified, and committed to the source code repository. To compile, a build is initiated to compile objects in a specified library from source code in a specified IFS directory. Only code that has been changed from the previous build is compiled, as well as any upstream consumers of that code. Object and source dependencies are respected, so if, for example, the DDS is changed for a logical file, then the LF will be recompiled, as well as any modules that use it, plus any service programs or programs that include those modules. Likewise, if a header file is changed, then all code that `#include`s or `/include`s or `/copy`s it will be recompiled.
Do not place IBM confidential, company confidential, or personal information into any field.