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 (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.

Add a new idea Subscribe
Status Future consideration
Workspace AIX
Created by Guest
Created on Jun 15, 2022

RELATED IDEAS

Harmonize procedure of managing configfiles during update of filesets

From an old case we noticed, that procedure how config files are treated during update is fileset-specific. Procedure should be same for each and every config file and it should be easy to check what was done with the config file. It should cover three possible cases, e.g. copying it to /lpp/save.config like:

  1. Old config file was not changed and replaced by new file

  • <name>.save

  1. Old config file was changed and content was merged with new file

  • <name>.save +

  • <name>.merge (content of new file from fileset)

  1. Old config file was changed, but overwritten with new file without merge

  • <name>.save +

  • < name>.overwritten

Such a clear convention would make it easy to identify candidates which could cause problems after update.

In addition:

  • Deleted config files should not be restored during update (e.g. /etc/hosts.equiv)

Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.