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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace IBM i
Categories IBM i Access Family
Created by Guest
Created on Mar 15, 2022

PSHBTNFLD work like hotspot

In the emulator in Access Client Solutions, you can specify hotspots which render as actual 3D buttons. This is great.
Ironically, a PSHBTNFLD (Push _Button_ Field) does NOT render in the emulation as a 3D button.

It would be nice to have a PSHBTNFLD actually render as real 3-D buttons... like the hotspots! (The code to do that must already exist in the 5250 emulator).

For compatibility sake, perhaps you could add a new parameter on the PSHBTNFLD (*REALBTN or something like that) that would cause each of the PSHBTNCHC choices to be rendered as real buttons.

Use Case:

I have a screen that is filled with information. But the users want to see more info; and there's no room to add another Fx=This function key at the bottom. (I KNOW that there are others with this same problem).
My solution was to add a PSHBTNFLD and when clicked, my program calls the QUILNGTX API to show the additional info in a modal. It works great!

HOWEVER, I have to explain to the user that they need to click that PSHBTNFLD because it doesn't look like a button to them.

Idea priority Low
  • Guest
    Mar 22, 2022

    Thank you for submitting a Request For Enhancement. Adding a new parameter to PSHBTNFLD would require both a DDS change and a data stream change. That is not something we would consider doing. Switching the default view of PSHBTNFLD is also not something we would consider doing at this time. To solve the issue of not having enough room to add another Fx= function key, our suggestion is to use the same approach used by the system panels; add something like "F24=More keys".
    For these reasons, we are declining this request.