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...
support SSL for HTTP notification
Currently the production offer a functionnality to generate http notification about transfert event (file sended, file receipted - start/end). The XML notification is pushed to an URL using the HTTP protocol. The message only push metadata of the ...
We need a MEMO not case sensitive
see attached file
Having mode T or O dynamic in APIs through CXTransferSubmit in CX Unix (linux) for Societe Generale
Due to a concentration project at Societe Generale where all transfers are going to be concentrated in a Central Hub (SFG + CX) we faced an issue regarding the mixed of partners defined in mode T and Partners in mode O. In order to not multiply th...
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 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 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.
Connect:Express Zos : use of batch process P0B2DIR
Connect:Express Zos : with batch Process P0B2DIR, we want to use the function LIST and EXPORT with only one SPN (or SFN). today, we can use only these functions with PARTNER.NAME = *
CX Number of transfers requests in a mode
To have a MVS command (MODIFY to the CX address space) to query the number of requests in the CX which are in the mode we would specify in the command ('U' for the running requests for example).
CX/ZOS Possibility to swap the logging so it is not increasing indefinitely
In CX/ZOS, the SYSLOG and other ddnames are increasing indefinitely. If they are Sysouts, which is convenient, this can cause Spool problems. It would be great to have the possibility to swap them, as Z/OS offers it for the ddnames JESMSGLG and JE...
Do not place IBM confidential, company confidential, or personal information into any field.