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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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:
Old config file was not changed and replaced by new file
Old config file was changed and content was merged with new file
<name>.merge (content of new file from fileset)
Old config file was changed, but overwritten with new file without merge
Such a clear convention would make it easy to identify candidates which could cause problems after update.
Deleted config files should not be restored during update (e.g. /etc/hosts.equiv)
Do not place IBM confidential, company confidential, or personal information into any field.