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.
HP-Nonstop Connect:Direct Maxdelay
Request for Maxdelay feature in C:D HP NonStop. To wait for the completion of a submit statement or interval time completes.
Please Test and Certify SQL Server AlwaysOn for Connect Direct
Please test and certify Connect Direct support for SQL server AlwaysOn. Our infrastructure team is pushing us to move our Windows install of C:D to SQL Server 2012 Always On Availability Groups. Our lab advocate asked for this RFE as IBM has not t...
HA solution for Connect:Direct using replication
Since Cloud VMs are widely used these days, has IBM considered to certify HA solution for Connect:Direct on Cloud VMs without requiring OS-level clustering software such as Windows Clustering or Veritas Cluster Software (VCS) for Linux? Those OS-l...
Support for Type=simple startup method in systemd for Connect Direct
The systemd is the default system manager on RHEL 8. Connect Direct should support service startup through systemd using Type=simple startup method. User can use Type=forking with external (custom) startup script but this requires to create additi...
Support MS windows 2019 clustered servers for CD Windows install
As, Enterprise is moving towards the recent MS windows available version, CD should support clustering on 2019. Per IBM Sterling Connect:Direct system requirements published link, Connect:Direct will support MS windows 2019 on standalone and do N...
snode.work.path parameter for IBM Connect:Direct for Windows
The "snode.work.path" parameter is available in IBM Connect:Direct for UNIX while it is not in IBM Connect:Direct for Windows. The idea is to have similar functionality in Windows version. It will allow to share SNODE work files among nodes in a l...
Native Variables in Connect:Direct Unix
We currently use some of the native Connect variables in: Windows for Windows, Windows for Mainframe, and Windows for UNIX.However, we need to use these same variables from a UNIX server and we are having problems.Examples:% SUBDATE1 and% SUBTIMEI...
codepage translation tracing
Current versions of CDU and CDZ do not track calls to iconv for codepage translation in submitted process, even with max trace level 4. We need to see calls to iconv along with parameters.
CDW services should be running as non-system and non-admin user account
Our security assessment team found an issue with 'System' running CDW services by default. Although IBM allows a service account to run CDW services, it requires this account to be a member of local admin group. Either method causes security c...
Alt Comm outbound Retry feature
When failing to connect to primary host/ip, system uses alt com outbound to try alternate addresses. Should none of them work, system goes in retry state ONLY retrying with last hostIP in alt com outbound. This causes some retries to get stuck as...
Do not place IBM confidential, company confidential, or personal information into any field.