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.

Created by Guest
Created on Nov 12, 2025

Perform Batch Reanalysis on FA Originating LPAR in SYSPLEX

This idea would benefit all users who run Fault Analyzer in a sysplex environment, use Fault History Views that cover history files from different LPARs in said sysplex, and have LPAR specific dependencies where running the batch reanalysis on an LPAR that's different from the LPAR where the fault was originally captured would cause the reanalysis to fail. 

For example, this can happen when a shop is using an alias with symbolics that resolves to different libraries depending on the LPAR, and only the resolved library (per LPAR) is in the APF list.

This issue can be resolved by adding a feature to FA that when activated would add an LPAR affinity to the batch job that gets generated to perform the batch reanalysis. 
This is a quality-of-life request, as of course this can also be done manually by the user by updating the job card every time before submitting the reanalysis job.

Idea priority Low