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.
Not a problem in our environment - therefor no vote.
So far we never had any issues with that even with multiple controlling systems on one CEC. Also the Monitor1-time depends on the starting time of the netview stcs so there’s a low chance of monitor-runs at the same time.
Low priority for us. Nice to have
Another nice to have. For us, not a problem at this stage, but who knows.
Prio Low
Not voted: We haven’t had any issues with this. Runs default every 5 minutes in < 1 second, where start time seems to depend on when netview stc’s are initialized and therefor runs random across the plexes. So the chance that 2 Lpar run at the exact same time is 0.2% for us (and I think 0.001% for a third?)
Although we don't have any problems with Monitor 1, I think it should be possible to define a starting time of the monitor so that we are prepared if we encounter a problem.
FIS/Worldpay also has multiple K systems on each CEC. We have not seen this cause any capacity issue. I see where it could. No vote.
we don't find MONITOR1 a problem in our environment. (so not voting)
We run with the default value and with multiple Ksys on the same CEC and have no problems with it.
Just in case the tasks running with Monitor 1 will increase in the future it could be helpful to straighten the use of resources and have different start times Monitor 1 in the different systems or sysplexes.
The priority is low.
we love standard environments, but can understand your case. not needed for us though.