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.
See this idea on ideas.ibm.com
Prevent accidental IPL during installation of PTFS to be applied at a later date.
Menu PTF option 8, "Install Options for Program Temporary Fixes" is used to install downloaded PTFS to the IBMi. The default option 8 is, "Automatic IPL . . . . . . Y ". In all my years (since the beginning) on this platform I have always installed the PTFS like GROUP PTFS or CUM by changing that Automatic IPL value to N. We need a way either through SYSVALs by default it to 'N' instead or command key like PWRDWNSYS has to prevent the accidentally IPL
I have always been careful. I know users including myself that take a screen of the screen so in case something happens while loading the PTFS that I can prove that a IPL is not due to me
This is how a CASE could go down:
You install a group PTF, but expect to applied when you IPL next Sunday. Instead you accidentally IPL Tuesday afternoon. The rest of the day is lost for the users at this location. Best hope is to have it ready for the Asian users and the Group PTFS don't affect something that you have not have time to test.
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.
Service attribute PTF install type controls both how PTFs are applied and the IPL action. CHGSRVA PTFINSTYP(*DLYALL) can be used to default GO PTF to set all PTFs for delayed apply and not IPL (field Automatic IPL will be set to "N" on Install Options for Program Temporary Fixes panel). The PTF install type (PTFINSTYP) service attribute is shipped with a default of *DLYIPL, however, you can change this to *DLYALL so that any user of GO PTF will not have an "accidental" IPL.
CHGSRVA really just sets the default for applying PTF's, it doesn't control the IPL action at the end of the apply step.
as far as I know you can run CHGSRVA and change parameter PTFINSTYP