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.
IDz v16.x has the Db2 for z/OS functionality nested within the Remote Systems Explorer (RSE) perspective which adds unnecessary overhead and potential confusion to developers. Previous versions of IDz used a Data Source Explorer perspective which was autonomous, cleaner, and easier to use.
RSE uses a connection through the RSED z/OS started task to do its work. However, even though it is nested within RSE, Db2 for z/OS uses its own JDBC connection to Db2. There appears to be no functional dependency between Db2 for z/OS and RSE so by having Db2 for z/OS nested within the RSE perspective does not provide any advantage to the developer but requires unnecessary overhead.
Also, having the Db2 for z/OS connection nested within the RSE perspective can cause confusion because some shops (like mine) do not have RSED tasks running on all z/OS LPARS where a developer needs to connect through Db2 for z/OS. In such a scenario the developer must still create a RSE definition (which is a useless shell) as a “gateway” just to be able to see and set up the nested Db2 for z/OS definitions. Developers will be confused as to why they have no RSE functionality, but they do have Db2 functionality in the same perspective.
From a customer usability position the design would be much better if it were independent of the RSE perspective like what developers are/were accustomed to with Data Source Explorer in earlier versions of the IDz client.