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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Standardize Connect:Direct messages
Currently, Connect:Direct has multiple message qualifiers, making automation difficult. requirement is for the Connect:Direct address-space to use a consolidated standard message prefix
Provide control over who can use the SNODEID parameter
With SPOE, the SNODEID presents a security vulnerability. The SNODEID is hard-coded in the process in clear text. Anyone authorized to use CDZ and able to read the file where the SNODEID is coded, typically in the process library, can create and...
Allow greater flexibility when amending Secure+ parms
Having a process which is reliant on a person logging onto an ISPF panel to update something like a TLS setting is no longer tenable in a modern IT environment. Automation and self service are the order of the day and the way Secure+ updates are b...
Can Secure+ be made any simpler?
I spend a lot of time trying to figure out Secure+ screens. Is there any way they could add more help to PF1?
Enable Transfer of Entire USS Directory via C:D z/OS
Sending Unix files on Z via C:D is tedious at best. I'd like for Connect:Direct to at least be on par with FTP functionality-wise if I'm going to try to convince users that it's in fact the better choice. C:D needs to be able to transfer an entire...
Secure Plus Error Message Enhancement
Is there any way to capture the SNODE name for which the SSL Handshake failure occurring with the error message CAPA202E, since the affected SNODE name is not present in the same line? We are able to find SVTM055I message in the next line but it's...
Enchance Connect:Direct for OS390 to support PDS to PDSE object-type dataset transfer
Connect:Direct cannot perform PDS to PDSE object-type dataset COPY.
ConnectDirect to throw message when it gets hung.
If ConnectDirect is hung there is no way to tell if it is, there must be a heartbeat check to confirm if NDM is healthy.
To authenticate users/applications based on the Certificates rather than using userid and passwords
Currently, Any user trying to access NDM has to logon with userid and password either manually or via batch jobs. In order to avoid clear text passwords, Users can be authenticated based on certificates.
SMS Compressed Dataset Enhancement with NDM
Visa would like to see Connect Direct transmission of SMS compressed datasets improved. Today, when we transmit a compressed dataset, if it is done with out coding the DCB parms in the process it always fails on the remote node with a space abend....