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.
-
Provide SUBMIT ESF=YES feature for CONNECT:Direct-Unix
On C:D-z/OS, an Extended Submit Facility (ESF) option (syntax is ESF=YES) exists for the SUBMIT command to allow C:D transmission requests to be queued up even when C:D is down on the z/OS system; the requests are executed later when C:D has come ...
-
Document all special characters that are not allowed in a Connect:Direct related password (functional auth, soliddb password)
There are some special characters that will not be accepted in Connect:Direct and IBM has not officially identified these for customers. We need this information.
-
Have C:D log the expiration date of certificates it receives
Today, when C:D calls out to a remote server, it logs some details about the certificate it received. It would be nice if it also logged the expiration date. This would allow us to write, say, a Perl script to scan the logs once a day looking for ...
-
SMTP connections
We require that the SMTP connection used for notification, to be retried in the event the SMTP server is down. This could be retried x times prior to giving up. Also would it be possible to specify a secondary SMTP server in the event the primary ...
-
"%Complete" field failure with file great then 4,3GB
Command WRKCDPROC- function Display C:D Process with file greather then 4,3 GB, field "%Complete" showing wrong value greather then 100%. Printscreen of this state is attached. PMR ID: 15921,668,668
-
FileAgent - Windows .ser file cleartext
Have the Default_Config.ser or other .ser files clear text or similar.
-
owner and private authorities for the new IFS object on system i
Please for change security design of C:D for system i. The incoming files to IFS on system i by C:D RMTSYSTEM job are created with owner CDADMIN and public *RWX authority. This causes lead to significant problems in further processing of these obj...
-
Certificate tracking in Secure+
Request that statistics capture serial numbers of SSL certificates exchanged during CD secure+ file transfers between pnode and snode. Serial numbers should be visible in select statistics and CD Requester.
-
delete file by C:D API not by RUN TASK&RUN JOB for windows
Now we delete file by C:D using RUN TASK or RUN JOB,we want to delete file by CD API not system command.
-
delete file by C:D API not by RUN TASK&RUN JOB for unix
Now we delete file by C:D using RUN TASK or RUN JOB,we want to delete file by CD API not system command.
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.
0
Planned for future release