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 Not under consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Jan 30, 2024

QGYOLOBJ does not return Information_Status = 'L' value and it should

The QGYOLOBJ has key 201 as well as a base header that includes the same information as key 201. However, that field, "Information_Status" or Key 201 never includes the 'L' flag (locked). Instead it returns blanks when an object is locked. So either the documentation is incorrect and needs to be changed, or the API is simply missing that functionality. Without this the only way to test for locks is using another API to list all the locks on the object and parse through them. (NOTE: This is a non-SQL App, so the SQL Services aren't beneficial). 

Idea priority Low
  • Guest
    Reply
    |
    Mar 15, 2024
    The QGYOLOBJ API is working as designed. The information status field will have a value of 'L' only if the object is locked with an *EXCL (Lock exclusive no read) lock in another thread and the object could not be locked by the QGYOLOBJ API.


    IBM Power Systems Development
  • Guest
    Reply
    |
    Feb 20, 2024

    Yes. I have 12 keys being returned, and one of them is the Status.

    However, the object(s) where I'm not seeing the Locked Status are locked with *EXCLRD not just *EXCL so that may be why it isn't returning locked.

    This history behind this requirement is that I am using QUSRUSAT (Retrieve User Space Attributes) which was going into a long-wait when the *USRSPC is locked with *EXCLRD. So I wanted to check that before attempting the QUSRUSAT API. But QGYOLOBJ isn't returning the "L" status when *EXCLRD is being applied to the object, so the routine failed. I'll write a function that calls the List Object Locks API and then check if there's an *EXCL or *EXCLRD hold on the objects and proceed accordingly.

  • Guest
    Reply
    |
    Feb 16, 2024
    On your call to the QGYOLOBJ API, are you specifying to return at least one key field?

    The QGYOLOBJ API documentation states that a key field must be returned for the information status field to be returned:
    Information status. Whether the QGYOLOBJ API returns the requested information for this object. If you do not request any keys to be returned, ignore this field.

    QGYOLOBJ API documentation: https://www.ibm.com/docs/api/v1/content/ssw_ibm_i_75/apis/qgyolobj.htm

    Also, the information status field will have a value of 'L' only if the object is locked with an *EXCL (Lock exclusive no read)
    lock in another thread.


    IBM Power Systems Development
  • Guest
    Reply
    |
    Feb 16, 2024
    On your call to the QGYOLOBJ API, are you specifying to return at least one key field?

    The QGYOLOBJ API documentation states that a key field must be returned for the information status field to be returned:
    Information status. Whether the QGYOLOBJ API returns the requested information for this object. If you do not request any keys to be returned, ignore this field.

    QGYOLOBJ API documentation: https://www.ibm.com/docs/api/v1/content/ssw_ibm_i_75/apis/qgyolobj.htm

    Also, the information status field will have a value of 'L' only if the object is locked with an *EXCL (Lock exclusive no read) lock in another thread.


    IBM Power Systems Development