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 currently using the GUI but this is a good idea - low priority
When we eventually get to use the GUI, this will be nice to have - low priority
Will be helpful- high
Do not use GDPS GUI (yet) ... however ... this is a good idea and valid request ...
A very good idea - Medium
As part of the activation of a changed GEODEF member the new options should be synchronized by GDPS to keep the GEODEF members in sync and prevent problems in the future when nobody remembers what was changed and why GDPS behaves different. Prio: medium
It is always possible that an update by use of the gui is followed by an event before you would manualy update the same dataset at the other lpar. It would be a very good addition to the gui to keep both sides in sync. (more reason to use it)
Not using yet the GDPS GUI, but for sure we need to avoid risk of data sets members being OoS.
Currently not using the GPS GUI, this doesn't apply (yet). But the options and scripts, which were previously kept in the SA policy, had to be maintained in sync (via "where used" constructs) and updates applied in sync, by the SA sysprog. Now that those have been "externalized" and are probably maintained by someone "other than" the SA sysprog, the need for synchronized distribution has not changed. I would not require GDPS to do the "update" of the GEODEF dataset.
(no vote..)