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 - Other
Created by Guest
Created on Mar 12, 2024

Simplify multilingual support by changing CRTDSPF and CRTPRTF to support new MSGCON parameter "Resolve MSGCON MsgID values at" *COMPILE (default) *RUNTIME (optional)

Multilingual support can be greatly simplified if IBM supports resolving MSGCON messages at *RUNTIME.

Currently MSGCON messages are resolved at compile time only (not good).  This is problematic because it locks-in compile time values to object which forces us to create environment/language specific objects for every DSPF/PRTF (not good).  If we want to change a message we're forced to recreate all the DSPF/PRTF objects that use it (not good).  We want a single DSPF/PRTF to be able to support all environment/languages by resolving desired environment/language objects and message content at run time using library list (good)(e.g. message file KML exists in libraries devENG, tstENG, prdENG, devFRN, tstFRN, prdFRN, devSPN, tstSPN, prdSPN)(if we want Production Environment to display content in Spanish we simply set production library list and add prdSPN library to top of list).

Idea priority Urgent