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
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
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.
System Recovery Boost is available with OA58302 (sa 4.1 and higher) on a mainframe z15 and higher.
You have to take care that Boost itself is enabled for the treated LPAR(s).
JCL procedure IEASDBS (triggering the boost via JCL) should placed in the PROCLIB concatenation appropriately. The JCL procedure name must be IEASDBS.
When shutting down an LPAR SA (within a GDPS environment invoked on the control system) issues by itself the according INGREQ ALL against the treated LPAR. The INGREQ command contains a BOOST parameter. Its default is YES.
If the default is not explicitly overriden via BOOST=NO (injected by an administrator) then SA verifies on the target LPAR whether it is enabled for boost and whether it is already boosting.
If is the LPAR is eligible but boost is not initiated yet then SA invokes the short running JCL procedure IEASDBS to trigger boosting.
For verification you may look into the syslog of the shut down LPAR and verify the occurrence of messages IEA675I and/or IEA681I indicating the start of the boost.
Since we assume that the described solution works we "Reject" this defect. Pls. try this suggested solution - and if its not working pls. open a defect with our support.
Thank you for your reply. We decided trying to recreate the scenario on our systems. When we have news and/or questions we come back to you again.
For shutting down a group of systems we use a rexx that calls GDPS scripts (for the actual shutdown) which results in INGREQ.
The rexx will call a GDPS script to shutdown the first system and monitor the shutdown.
When the first system is shutdown the rexx will start the shutdown of the next system.
This will repeat until all required systems are shutdown.
Thans for submitting this requests for enhancement, Currently we are reviewing it - and try to understand your scenario.
The boost should work for every system independently. We try to understand how a shutdown of one system can influence the shutdown of another.
In your scenario can you pls. explain how you shutdown the whole system - did you do it individually with INGREQ system by system? Or what is
the process you are doing it?