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.
This feature was delivered in version 9.5.1.1.
VSEDDM was the old way to remotely access VSAM files on VSE. It used VSE Connector Server (VCS) as the VSE back-end. It is no longer the preferred way to remotely access VSE VSAM files, and we don't think it will be enhanced to support all three points. VSEDDM is maintained by VSE support team not RBD.
We can change RBD to use VSE Connector Client instead of VSEDDM to remotely access VSE VSAM files. It supports 64bit RBD, you can specify the VCS port number and it supports SAM ESDS. RBD already uses VSE Connector Client for COBOL generation and Remote DL/I.
If I understand this correctly, the main functional problem is that the VSE DDM implementation in RBD does not support accessing SAM ESDS files.
Native Java API of VSE Connector would support that.
Due to that, replacement of current DDM based remote VSE file access with VSE Connector Client implementation would be a genuine enhancement (probably also in view of having remote VSE file access feature in 64bit releases of RBD).
I strongly support this RFE!