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 Core OS
Created by Guest
Created on Jan 30, 2020

Fix QsnRtvWinD so that it correctly returns its information

The DSM API QsnRtvWinD does not correctly populate the passed in data structure with the current window description. This causes errors when using that information in the QsnChgWin API--for example, the window border will not recognize the GUI_Support flag.

Use Case:

Using DSM to create displays for applications is challenging when the APIs don't work. This API is used to allow our users to customize the look of the Window dynamically. However, when used, the window reverts to "text" border (dots) instead of the "cooler" GUI look.

Idea priority Medium
  • Guest
    Mar 12, 2021

    At this point, we do not have enough information to provide any sort of resolution. It would be best to submit a Services Case for this and to provide a test case where we can see what is happening. This appears from this description to be a defect vs a new enhancement.

  • Guest
    Mar 12, 2021

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Core OS
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Application Development
    Operating system - IBM i
    Source - None

  • Guest
    Jul 7, 2020

    I'll have to go find my documentation I wrote on this but from memory:
    Use QsnInzWinD to initialize a Qsn_Win_Desc_T
    Use QsnCrtWin to create a window using that Qsn_Win_Desc_T structure.
    Next, attempt to change the Window layout, so I:
    Use QsnRtvWinD to retrieve the existing Window's description.
    Then call QsnChgWin to perform the change. It fails with Invalid Data in Qsn_Win_Desc_T structure.
    At this point, not all data was returned into the structure.
    My Workaround is to use a 2nd Qsn_Win_Desc_T structure and save the original information then use that saved information while performing the QsnChgWin function.
    Since posting this, I have continued to use the workaround so I don't have the specific code that caused the initial issue. But this is the summary.

  • Guest
    Jul 6, 2020

    Can you please provide examples of what is incorrect. Not able to make an assessment with existing information.