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.
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, ...
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...
Provide additional information when Session High Water Mark is reached
For Product id 5665-X09, record the number of active PRIMARY (PNODE) sessions and the number of active SECONDARY (SNODE) sessions when the session high water mark is reached. Record as much additional information as is reasonably possible in the ...
C:D for z/OS to support the allocation of PDSE V2 datasets
Currently, IBM Sterling Connect:Direct for z/OS (CDZ) does not support the allocation of PDSE Verion 2 (V2) data sets. Customer has the requirement to use the CDZ function to transfer PDSE V2 data sets for program deployment between testing and p...
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...
CD for z/OS - customisation of ISPF panel library for scroll amounts & CF enhancement
Hi. I have 2 enhancement requests, but they both relate to the ISPF panels for CD for zOS.
1. The default scroll amount on various panels is set to PAGE. I think the CSR setting is more flexible. As the panels do not remember your settings, I ...
Enhance STATs Log TP Record to Report Send and Receive Time Count
This is the enhancement request per email discussion to enhance TP Records to Report Send and Receive Time Count in the time interval.
Have statistics Records (CT and maybe others) indicate the true node a transfer was sent to when ALT.NODEDEF is coded in the Netmap for a node
Currently if two nodes are defined NODEA and NODEB in the netmap and NODEA has ALT.NODEDEF=NODEB coded, if NODEA can not sent to its primary IP address coded then the file will be sent to the IP address coded on NODEB. The issue is that the CT s...
Do not place IBM confidential, company confidential, or personal information into any field.