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.
Ver display on IUI panel
If there are multiple instances of different NDM ver running, it will be easier to identify if the IUI panel has ver displayed. Attached screenshot will give the idea of what i meant. In this the right-side box has ver hardcoded. if there is a pan...
Security Exit must be usable by different SFTs and the STCname should be part of the RACF profile namess
In our environment we run several Connect:Direct stc's in one environment.The provided Security Exits do not offer a possibility to setup separate profiles for these stc's.We would like this to be changed.Second what we ask for is to add the STCna...
Support the use RACF PROTECTED userids in the Secure Point of Entry (SPOE)
When we create User IDs in RACF that will be used for Connect Direct transmissions, we have to create them with passwords so that the password can be used in the SPOE record. With a password is can make this User ID have the capability to sign...
Status "Wait Queue" on SMF record
Add the Wait Queue" statuses (WC, WP, WT, and WX) in the SMF records.
Improve diagnostic accuracy of Secure+ error messages
We often get Secure+ error messages (prefix CSPA) that don’t necessarily indicate a Secure+ issue. This makes it difficult to monitor for errors. The error messages that have caused us the most difficulty are:
CSPA202E SSL handshake failure, ...
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...
Include transfer rates monitoring on active filetransfers
Please include file transfer rate monitoring mechanism on active filetransfers. We had an issue with partner where after partner side upgrade the transfer rate became very slow. The filetransfer that took previously minutes, was now hours long. Sa...
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?
Issue a message when CDz reached NODE Specific Max PARSESS Limit
CDz does issue SVTM082I when CDz as node hit the node specific SESS.SNODE.MAX. However, it doesn't issue any message when it reached Max PARSESS. Could you add a corresponding message for this so that we can easily figure out it hit the limit?
Extensions to Compress with Connect:Direct
Our clients who are transferring from Connect:Direct are using windows.However, because of the smaller lrecl of the file being transferred, it will not be compressed for the following third specification:1) CD z/OS to CD z/OS transfer will be in b...
Do not place IBM confidential, company confidential, or personal information into any field.