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
Created by Guest
Created on Sep 30, 2022

Extend WRKJOB (or new SQL service) to show open descriptors of a job

When analyzing issues some times I must also check how many descriptors a job has in use. In case of f_type VNODE I will also check the IFS path.

To get these information I must execute the following statement:


Then go into the created spool file QSYSPRT and search for "*** Descriptor table". It is at the end of the spool.

Like showing the environment variables in WRKJOB using the new option 22 (in older IBM i release I had to execute CALL QSYS/QP0ZMAINT ('30'&X_JOBNBR'0''30')) I wish there is a new option 23 to show the in use descriptors of a job.

Idea priority Medium
  • Guest
    Oct 28, 2022
    After investigating further, we understand that there is no straightforward and approved interface for users to display open descriptors in a job. We will consider how we can do this better.

    IBM i Development team.
  • Guest
    Oct 26, 2022

    Yes, the actual in-use descriptors of a job and the descriptor limit of the job are very important. The default descriptor limit of a IBM i job is 200. When a program does not close socket descriptors or IFS file descriptors the limit will be reached and then I want to see which descriptor types are in use. With this information I can check which program must be fixed.

  • Guest
    Oct 26, 2022
    The QP0FPTOS functions are intended for service.

    There are 2 methods to get the objects being used by a job.
    The Retrieve Referenced Objects (QP0LRRO) API will determine what file system objects are 'in use'. This will include the current directory, 'root' for the job, and any objects in the descriptor table. This API returns a count of objects in use as well as additional information for each job.

    The IFS_JOB_INFO SQL table function returns similar information to the QP0LRRO API.

    Is it necessary to see the actual descriptors being used?

    IBM i Development team.

API/Command to Monitor File/Socket Descriptor

Currently, in order to monitor the file/socket descriptor of those jobs we need the job number and put it in the CALL QP0FPTOS PARM(*DUMPLFS 'xxx') command and see the value of each job on each spoolfile. There are more than 50 jobs that the cus...
over 1 year ago in IBM i / IFS (Integrated File System) and Servers 2 Future consideration