Skip to Main Content
IBM Power 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:

Post your ideas

Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas and add comments to ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Specific link you will want to bookmark for future use

IBM Unified Ideas Portal - - Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.

Status Future consideration
Workspace IBM i
Created by Guest
Created on Oct 11, 2019

support externally described programs and service programs

Program objects (*PGMs, *MODULEs, *SRVPGMs) should support "reflection" so that the interface(s) are "visible" so that it is no longer necessary to hand code and maintain "/COPY book members" (1960s technology.)

Back around V5R2, IBM began adding PCML support to some ILE languages, so they can be more easily used with tooling such as IWS. That was a great "first step."

I propose to take this to its logical conclusion -- extend the PCML so that it covers all of the possible data types of the parameters etc., such that any other language compiler, instead of having to use a "/INCLUDE" statement to pull in the source code for a definition of the externally exported interfaces, can use a statement such as:

uses pgmName.PGM;
imports srvPgmName.SRVPGM;
import moduleName.MODULE;

and those compilers will use the embedded PCML to extract the needed definitions.

Also, the "uses" or "import" statement should permit optional "library qualification," for example:


This will go a long way towards making IBM i the truly modern object-based OS that it was intended to be.

This will greatly reduce the possibility of runtime errors and storage overlays and corruption due to mismatches between the "definition" (/COPY book) used at "compile time" and the actual generated code executed at runtime, thereby further improving the reliability and integrity of the platform.

Ideally, the compilers can generate some kind of a "hash" or "signature" over the parameters as well as the procedure names, so that at runtime, when a program or service program first references (and activates) another *PGM or *SRVPGM, it can check these signatures just once, at initialization time, and detect any "mismatch" between the definition used when the calling program or service program was originally created, and the *PGM or *SRVPGM that is about to be used at runtime.

This is analogous to the OS/400 database "record format Level ID" and compiler generated code to perform a "Level Check" at file OPEN time, to prevent similar disasters where the record layout used at compile time no longer matches the actual database file record layout. This feature has likely prevented may serious problems where data could otherwise be "corrupted" in customer database files.

A similar feature for compiled *MODULEs, *PGMs and *SRVPGMs will provide similar benefits.

The "good news" is, IBM has already added some PCML support. So, IBM can just build upon that as a foundation, to create the needed capabilities.

Use Case:

Many modern languages such as Java support a similar mechanism, where you simply state:

use packageName;

to import the definitions from the .class or .jar file.

This is also similar to modern languages such as Python, node.js, etc.

There is also a movement in the ANSI C standard to add "modules" to ANSI C, for a similar purpose.

This support should also be extended to work with Java --since Java supports "reflection" it should be possible to code a statement such as:

use javaPackageName.class;
use javaPackageName.jar;

and the compilers should be able to extract any needed definitions from the Java .classes using the "reflection" capabilities built into Java.

This would alleviate the error-prone process of having to manually define the interface to the Java methods, etc.

Idea priority High
  • Guest
    Mar 24, 2020

    The CAAC has reviewed this requirement and recommends that IBM view this as a medium priority requirement that should be addressed. It is essential that IBM i does all it can to keep current with other languages. PCML really does need to be extended.

    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

    For more details about CAAC's role with RFEs, see

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Feb 17, 2020

    The COMMON Europe Advisory Council (CEAC) has reviewed this requirement and recommends that IBM view this as a MEDIUM priority requirement that should be addressed.

    Background: The CEAC members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial 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.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ and the article "The Five Hottest IBM i RFEs Of The Quarter" at

    Therese Eaton – CEAC Program Manager, IBM

  • Guest
    Oct 23, 2019


    Maybe also eliminate the need to code the prototype twice (in the called and calling procedures) for external procedures. The compiler should find the called service program, and from it the called module / procedure and copy from there the prototype. Similar to RPG built in functions, that no prototype is needed.

  • Guest
    Oct 12, 2019

    I have A similar idea. perhaps a _meta_ procedure could expose all exports and parameter descriptions ( In JSON) that describe features of a service program etc. that means that webservices and code completion could be done automatically.

    A candidate for a new RFE

  • Guest
    Oct 11, 2019

    Attachment (Description): This presentation describes the idea in terms of how to enhance the ANSI C language to include this kind of functionality, called "modules" in C. If you look at this presentation, you should be able to understand how the same kinds of issues exist with ILE RPG IV compiler built-in pre-processor /include and /define mechanisms. Also similar for COBOL with its COPY mechanism.