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).
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.
Medium priority.
You could add the following statement in any hyperswap script:
IPLTYPE=SYSTEM(ksys) MODE=RSn
This should work as a circumvention.
By the way, before reading this idea I was not aware of the problem. So thank you!
This is not a priority for LBG over the next two years.
We submiited RFE 83696 was back in 2016 which was along these lines, but I don't think it was incorporated (we'd need to re-test). If you could locate the docs with this RFE maybe that would help, or I could find my copies from the time.
Basically, we use SubChanSet 1 for the Secs and need a RS2 LOADxx member for the Ksystems with "1" instead of "*" whenever a Pri>Sec Swap is done, due to the way an IPL locates the SCS on IPLing (Ksystem volumes are in SSC-0), otherwise NIP has problems.
I seem to remember a SysplexWideIPL from RS2 (for whatever reason), starting with the primary Ksystem, was the main problem.
We would like to understand what kind of variations you have based on the replication site?
In theory, no matter what is the current replication site, the production system devices should be offline at IPL for instance so we do not see the need of having multiple OSconfig.