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.
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)
To have the possibility to desactivate the protocols ODETTE and ETEBAC3
To have a parameter in the SYSIN of CX to desactivate the protocols ODETTE and ETEBAC3.
CX Command STANDBY to go to the XRF member : must verify that the XRF member is ready
In CONNECT:EXPRESS (CX) , when we pass the Modify command STANDBY, it must be refused by CX if the XRF member is not ready.
At this moment the IBM MQSC adapter has a -CD option for channel definition but there is no way to specify a CCDT file for secure connections
We use WTX with launcher on AIX . Until now, with 1 CCDT we only had to set the environment variables MQCHLLIB, MQCHLTAB, MQSSLKEYR to point to a single CCDT-file. These envrionment variables are set before WTX is started and so every map of every...
Allowing multiple certificates with the same common name and subject to be loaded into the JAVA Key store for Secure+
Connect Direct 4.2 Secure+ JAVA key store does not allow for multiple certificates with the same common name and subject but with different serials and expiration dates to be loaded. Only one will load. We have this issue with our FRB, DevTOCA, ...
Currently there is no way to interrogate an lu or adjacent node in ndmcom or other utility to see what was the last time the snode was used.To evaluate usage patterns, we would like a RFE to have a useful tool to track last used timestamp at the n...
Request Spooler Option print process to include milliseconds in time
Since we've upgraded to the HP Nonstop NS2400 from the S-series, printjobs are hitting the spooler so fast that using the Spooler Optioncreates duplicate filenames at the target server. This causes many jobstransfers to fail due to duplicate names...
Connect Direct defaults to a 002 umask on unix platforms
Files delivered to unix systems are given rw-rw-r-- pemissions as CD is not recognising the system umask of 027 and is defaulting to 002.
Log Aged Processes for Recovery Purposes
When processes exceed the MAX.AGE initialization parameter value and are purged from the queue at the MAX.AGE.TOD setting value, NDM should write out something listing at least the process numbers that were removed in case any of them needed to stay.
Auditing Feature to iSeries C:D
Good Afternoon, i would like to see the auditing feature in your current product Sterling Gentran being added to Sterling Connect Direct.
Do not place IBM confidential, company confidential, or personal information into any field.