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.
It would be very interesting if batch scripts were included in this idea scope. We also have cases of time reduction for operations that are executed via batch type script.
Yes please, sounds like a useful idea.
as always… the more parallelism the better…
This requirement would be considered a 'nice to have' for LBG, i.e., low priority and not something we'd need within the next two years.
Having the ability to run multiple scripts or Standard actions at one time would be greatly beneficial.
Not being able to reset or perform a Standalone dump on a system because another system is involved in a shutdown.
You should be able to invoke similar actions at the same time as well. Shutting down an image and then 5 minutes later invoke a shutdown of another image. This should not cause confusion to GDPS and it should be able to track these items as seperate functions.
We have some inconvenience for waiting on scripts to end before we can start new ones, but those are mainly when we Stop, Load, Activate and Deactivate Lpars, so basically the "standard actions".
Be aware, currently without parallelism there is an automatic safety net that conflicting scripts could be running at the same time. When parallelism is made possible we should not introduce the possibility of having conflicting scripts running at the same time. Safety first.
Would be helpful to start IPLs in parallel
nice to have for us
Being able to run system shutdown and IPL scripts in parallel would be a great improvement for BAU and recovery scenarios.
I support the idea of enhanced parallel processing regarding Scripts.
Parallelism would be greatly appreciated
Yes, anything involving BCPii takes a while, so speeding recovery up via parallelism would be appreciated.
This suggestion and the ability to have a script initiate another would be nice to have.
We are also looking to implement more parallelism in our GDPS scripts. If we could execute a CBU activation during our DASD recovery and have those streams running in parallel, that would be very helpful. There would be other use cases as well.