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 Needs more information
Workspace IBM i
Created by Guest
Created on Feb 14, 2024

New API to return a Pointer to Associated Space of User-Objects

Today, some objects on the IBM i system do not have a DSPxxx command that supports either OUTFILE or in some rare cases, no DSPxxx command at all. In addition there is no API to get some of these object's properties.

This request is to provide an API in the spirit of QUSPTRUS, but QUSPTRAS (Pointer to Associated Space) which would return a pointer (it can be read-only pointer) to the associated Space for a given object. Today, *MENU, *CMD, *BNDDIR are some of the objects I'd like to be able to read the information stored in their associated space.

This will provide us with the ability to retrieve things like a *MENU object's attributes (Type, associated Message file), or *BNDDIR the actual entries in that binding directory.

We do mostly C/C++ development and the ability to get to this stuff without reading it in a SPOOLED file or similar, would be wonderful. We used to be able to do that decades ago, but now with QSECURITY(40) on just about every system, we need an API to get to that kind of info.

Thanks.

Idea priority Medium
  • Guest
    Reply
    |
    Aug 27, 2024

    Only for Binding Directories but not for the other objects, obviously. :)

    Also, I don't like the idea of having to create a file with the data that is produced by an interface that reads the data directly. I should also have access to that interface. Message Files, Menus, CL Commands, all have a similar requirement and we used to be able to get to that info. In fact, I once wrote a C program that read the *CMD object and re-generated the Command Definition Source that was used to create the command. That kind of ability no longer exists and I am of the opinion that it should exist. Thanks!

  • Guest
    Reply
    |
    Aug 27, 2024
    The DSPBNDDIR command does have OUTFILE support and I believe the value you are after is there. Will that work ?