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 Connect:Direct messages
Currently, Connect:Direct has multiple message qualifiers, making automation difficult. requirement is for the Connect:Direct address-space to use a consolidated standard message prefix
ConnectDirect to throw message when it gets hung.
If ConnectDirect is hung there is no way to tell if it is, there must be a heartbeat check to confirm if NDM is healthy.
To authenticate users/applications based on the Certificates rather than using userid and passwords
Currently, Any user trying to access NDM has to logon with userid and password either manually or via batch jobs. In order to avoid clear text passwords, Users can be authenticated based on certificates.
Improve on C:D z/OS the last STEP COPY with all information after many restarts on the File Transfer incoming traffic
Description: To avoid information inconsistency of the STEP COPY (restart) of the file received and the C:D statistics information as records and VTAM bytes. Proposal is for C:D z/OS Caching all of the STEP COPY (restart) information on incoming F...
Provide additional granularity for the UPPER.CASE= initialization parameter
Currently, as documented in the C:D for zOS V5.2 Administration Guide, the UPPER.CASE= parameter determines if initialization messages are send to the console in Upper (YES) or Lower/Mixed case (NO). However, this parameter also dictates if inform...
Improve on C:D z/OS the caching all of the RACF userid support on the File Transfer incoming traffic
Description: To reduce the allocation time of a file, would be better to implement on the C:D z/OS the caching of all userid that RACF (ACEE) support on the inbound traffic, that is basically to memorize the accesses and minimize the queries to th...
Enhance C:D to provide better support for zEDC datasets
We are implementing zEDC across our production environment and are trying to avoid mass updates to all of our C:D processes.
We would like to be able to transmit a zEDC dataset without having to update hundreds of existing processes.
Connect:Direct for zOS copying files to SNODE (Linux or Windows ) at the same time using a '*' mask to individual datasets
The client SERPRO would like that was possible in Connect:Direct CDP pull a list of datasets that meet your dataset mask with the '*' (for eg. ABCDEF*.TXT)and based on that list of datasets that match then to start copies each of the datasets one ...
Manage NDM for z/OS from Windows NDM
Like DB2 explorer, allow NDM for Windows act as a management client, to show and manage NDM for z/OS. Such as copyfile, manage queues, even display/update Netmap.
C:D Link failure mesage ids - SVTN001I and SVTO022I documentation
There are few of the transfers ended (failed) with connect: direct completion code 10 along with completion link failure message text SVTN001I and SVTO022I. We checked under below path for the allocation errors message id along with max retry limi...
Do not place IBM confidential, company confidential, or personal information into any field.