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.
-
Propagate DSNTYPE values between z/OS systems
Consider cloning the DSNTYPE values for transfers between z/OS systems by the default.
Shouldn't be necessary to specify them if the source dataset must be the same as the destination
-
converting Node reservation(node1) into Node Demand(node2)
For DFS(delivery from store) often times a reservation made aginst a store may have to be reassigned to a different store due to inventory reasons. The legacy OMS makes the determination to resource to the second node.
Note: For this implementatio...
-
automated cddef.bin creation via lcu.bat by passing positional paramters
I want to create cddef.bin automatically via script. Thus I want to pass all values to lcu.bat via positional paramters rather than interactively. e.g. lcu.bat %NODENAME% %IPADDRESS% 1363 %CD_UID% %CD_PWD% %CD_PWD%
-
Enable SequenceGenerationKey usage in Router Action step
Currently, SequenceGenerationKey is only enabled to use with Basic transation action. It will be very helpful if we have access to use this with other actions too. ( Example : Enveloping, Router etc )
-
Group system in userfile.cfg (UNIX)
In an environment with hundreds of users defined in the same userfile.cfg, it would be nice to be able to govern them through a system of groups or profiles to reduce administration time and avoid unnecessary failures.
-
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...
-
Apply maintenance on a multi-LPAR CDPLEX
Currently, to apply maintenance to a CDPLEX that is in more than one LPARs, we must stop the entire CDPLEX and apply maintenance to the entire group at the same time. In a case to support they told that this is so because the Manager could have pr...
-
RestAPIs support to Create/Update and Delete MAP Files
This will help us to include Maps for our CICD Pipeline where we are updating B2Bi Assets using B2Bi RestAPIs.
-
Add a status field on Inflight under Business Field1 to find out only the status of "Finish" documents
Many Support Users from GSK are asking if there is a way find Finish documents from Inflight from search criteria instead of looking into events. This feature will also be useful if there was a planned outage at partner of customer side to hold do...
-
Purpose field in pick request allows only two values SALE and TRANSFER, we need more values - REPLACEMENT, PICKUP
Purpose field in pick request is only allows two values SALE and TRANSFER, we need more values - REPLACEMENT, PICKUP. This will help store to differentiate what type of PICK request. We need purpose field value to be supported in pick preferences ...
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.
1
Functionality already exists