Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 z/OS
Categories BCP_Supervisor
Created by Guest
Created on Feb 8, 2024

Error message to be produced when LNKLST concatenation datasets experiencing severe performance degradation, especially Sys1.LINKLIB.

This will indicate that there is a problem with LNKLST concatenated datasets, and that LNKLST is is under performance degradation constraints, when datasets were removed and added back to the LNKLST concatenation.
Current error messages for LNKLST did not indicate any problems with LNKLST.

Idea priority Urgent
  • Guest
    Reply
    |
    Mar 5, 2024
    .z/OS does not track the performance of fetches from a data set, whether that data set be part of the LNKLST or not. I believe from the Case that the real problem was that the LNKLST as a whole was not being managed by the Library LookAside (LLA), after some unsupported operations were performed. As a result the retrieval of a module's directory entry was done using I/O to the dataset rather than in-storage retrieval for every module fetch from the LNKLST. You might consider submitting a request for a message informing if LLA is or is not managing the current LNKLST set as an entity (or that that state has changed from managing to not managing) since it is managing as an entity that allows avoiding some I/O to the dataset. Or you might be able to tell from monitoring programs such as RMF that unexpected I/O is occurring.