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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
I can highly recommend the suggested use of remote virtual image catalogs for storing IBM i media and PTF groups. We use the same method and have full control of the software level on all our IBM i partitions.
In our setup we have assigned one IBM i partition to host the software repository and store the software and fixes in image catalogs. We have also automated the PTF group ordering and download on the same partition. The repository is kept updated without any manual operation. We have two image catalogs for each IBM i release: one for IBM i media and one for PTF groups.
Since the image catalog is always up to date, when a partition needs to be updated we simply start the PTF install process using this catalog.
The PTF groups are installed in a staged process: First the PTF group is installed in a sandbox. If no issue is found, the catalog is copied to a QA catalog and PTF's are installed from this catalog onto the QA server. If no issues are found during the test phase, the QA catalog is then copied to a production catalog used for installing PTF on the production server.
We have developed our own CL command for copying an image catalog. It uses RSYNC to only copy changed image files, which speeds up the copy process.
Christian,
IBM Champion and CEAC member
We need to add a GRPLEVEL (Group Level) parameter to this proposal.
I just ran into a major issue upgrading 5 partitions for Infor Safran customer. Right in the middle of our upgrades, IBM released Java Group Level 22. Because SNDPTFORD forces the latest version, the command automatically pushed Level 22 onto the remaining partitions instead of the Level 21 we had thoroughly tested.
It introduced unmanaged risk into production mid-project. If we include a GRPLEVEL parameter alongside your RLS idea, we can finally freeze specific group levels right from the command line and prevent this from happening.
Thanking you in advance.