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 Future consideration
Workspace IBM i
Categories Core OS
Created by Guest
Created on Mar 1, 2022

Provide a way to check object lock/allocation beyond WKROBJLCK

When deleting a user library if an object in that library is being referenced by or if the library is on a library list of another job, that library cannot be deleted.
We need a way to know which jobs not only have the object locked, but also allocated.

Use Case:

There are many scenarios, but one is restoring a new version of a licensed program and the target library is on someone's library or if, for example, a VIEW is in that library and that view was accessed using 3-part naming, then a QZDxxxx job is created and doesn't release that VIEW for "centuries" in some cases.
Then if you go to delete that library where that view exists, the delete fails with an "in use" or "allocated to another job" message, but gives no indication of what that job is.

Idea priority Medium
  • Guest
    Mar 17, 2022

    We will consider this for a possible future enhancement.