Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 Future consideration
Created by Guest
Created on Jan 3, 2024

Relief IZWS PIF LIST Memory Storage Limitation

Our installation has written several IZWS Add-on components that extract data from the Current Plan. Some monitoring or live snapshots requests read the entire CPOP segments. Therefore, it happens, when there is more workload, that the PIF LIST is not able to return all the operations.

We found that the PIF LIST is still using pre-XA memory management, i.e. buffers under the 16-Meg line. In batch mode, we noticed that a PIF LIST running on the Controller's system in Local mode will use more memory (under the line), and therefore fail sooner then later. A bypass is to execute the same request in TCP mode, where less memory is required by IZWS, so more available to the PIF LIST buffers, but still under the 16-Meg line.

With the introduction of XA, ESA, and zArch, filling the buffers to architecture's maximum capacity should never be an issue. Our request is to remove the storage limitation, which would not only benefit to native PIF code, but probably to other interface like EQQYCAIN, EQQYLTOP, WAPL, OCL, DWC and the REST API.


Idea priority High
  • Guest
    Reply
    |
    Jan 12, 2024

    In Case TS008409324, IBM L3 support wrote: "This kind of changes is not complex from a local point of view but cannot be implemented as a fix, since customers might rely on the current behavior and any change might have consequences that should be evaluated by the development. Changing EQQYCOM call would imply the need to recompile PIFs and change the engine of this rc setting in EQQXSSRR might impact other scenarios and might need a new parameter to allow the option." In the same Case, IBM delivered APAR PH44895 (RC=0 IS RETURNED AS DESIGNED WHEN THE LIST IS INCOMPLETE) that added the OPCOPTS PIFLISTRC option. This is the same kind of simple change that would be required here to relief our add-on monitoring and history query components.