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.
MQ notifications on CX
When notifications are sent using HTTP, as you only have one HTTP server to send the notification you cannot do any load balancing between multiple nodes. If HTTP server answers too slowly due to a large load, HTTP response code can be sent before...
We need a MEMO not case sensitive
see attached file
Purging notification records at run-time
With current Windows Connect:Express versions, when notifications are enabled, notification records are added at run-time in the local database, even when they are fully processed (notifications messages sent), and they remain there, possibly very...
CX SYSTCP Partial generic
In the SYSTCP the TCP/IP address can only be unique or '*'. It can't be gÃ©nÃ©rique like 172.016.063.* So we have too much entries.
Be able to customize the default location of logging files
It would be very useful to be able to change the location of the log files.Currently it's located on [CX]/config.
Handle spaces in physical name for Sterling Connect:Express UNIX
Actually, Sterling Connect:Express doesn't handle spaces in physical names for a PeSIT file transfert (sender's side)
CX SYSSSL IH higher priority than IA=*
In the SYSSSL PROFILE, if there is an entry with IH and an entry with IA=*, the IH entry could be used. Actually, it's the IA entry which is used because priority is on IA.
CX Direct access to tapes
CONNECT:EXPRESS FOR Z/OS could access directly tapes : read tape to transmit the file or write on tape the file received.
CX PCTADD & FCTADD Alert of filling
In CX we can have up to 999 memories to add the definition of a PARTNER and 999 memories to add the definition of a FILE. There is a need to have an alert when theses 999 memories are almost exhausted or a command to know how many are filled. Wh...
Possibility of overwriting sizes registration on Windows C:X
This request is for homogenization of functionalities on Windows such as Unix : Possibility of overwriting sizes registration defined on SFN configuration.(Format , length)