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.
-
Standardize SYSOPTS syntax for multi-environments
SYSOPTS syntax is written differently depending on the environment: Windows, i5/OS, z/OS, and UNIX. Example on z/OS: SYSOPTS = "DATATYPE(BINARY) XLATE(YES) STRIP.BLANKS(NO)" Same example on UNIX: sysopts=":datatype=binary:xlate=yes:pipe=yes:" This...
-
CD Requestor for Connect Direct UNIX
There needs to be a way within a Connect Direct UNIX environment to validate a process script without having to copy it on a Windows system and using CD Requestor there. It would be great if CD Requestor or something similar was to be implemented ...
-
Allowing command line editing of the CD File Agent configuration
There is a need within the Treasury to be able to script password changes to Connect Direct File Agents. Currently there is no documented way to accomplish this outside of using the GUI.
-
Automatic Control of Sessions between the client and partners to avoid Wait Sessions
If the client has in netmap configuration session limit defined and the partner has in their netmap configuration session limit different from the client, it will leave the process in wait and sometimes depending on the volume, Connect:Direct will...
-
Sterling Connect:Direct Application Interface for Java support to iSeries C:D version
CDJAI support all other platforms (Windows, Unix, ZOS and Tandem) except iSeries. This limitation restricts users to automate C:D configuration through CDJAI, similar to what we do in other platforms. Now we have to login to iSeries machine to do ...
-
Add detailed software version to .swidtag file
Currently the .swidtag contains version in V.R.M format so it is missing the exact Fix Level and iFix version. For example: version 6.1.0.2_iFix012 for Windows in the .swidtag contains version="6.1.0" and not the full 6.1.0.2_iFix012 (or 6.1.0.2.0...
-
FileAgent - Windows .ser file cleartext
Have the Default_Config.ser or other .ser files clear text or similar.
-
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...
-
Fix a bug which IBM support is not accepting as a bug
Problem: Any CD Windows v6 client or Requestor is impacted. When a lower case process name job is submitted, via the v6 client or requestor, the process name is automatically converted to uppercase and the job is submitted. While the same process ...
-
Status to be returned when performing an automatic silent install
When performing an automated silent install/upgrade from the Windows command prompt, instead of the command dropping straight back to the command prompt, certain messages would be returned and at the end of the install/upgrade a return code/status...
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.