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.
Add VICS version 6020 for download to WDI 3.3
We are moving to the VICS version 6020 of EDI and would like to be able to download the standards for WDI v3.3
WebSphere Data Interchange z/OS 3.3.0 and DB2 V12 for z/OS compatibility
From PMR# 43108,227,000, the latest supported DB2 version for WDI 3.3 on z/OS is V11. We are planning to upgrade to DB2 for z/OS V12 soon. Is WDI 3.3 compatible with DB2 V12, and are there any PTFs required to be compatible with DB2 V12 (function...
Please validate the latest Windows Server OS to work with WDI V3.3 and the client installs
Our server group is pushing the upgrade of all servers running Windows Server 2003 as it is EOL for support through Microsoft. The stress is on getting it to work in 2012 R2 as that is the preference.
We are planning to upgrade from z/OS 2.3 to 2.4 at the next year. Could you test this solution on your environment?
I was informed by Loan Vo that WDI 3.3.0 was fully tested at z/OS 2.2. We are already at z/OS 2.3, with no issues to WDI. My question is: Could you test this solution on your environment, using z/OS 2.4? Thanks a lot for you attention.
WDI support validation with AIX 7.2
We have WDI 3.3 running on AIX 7.1.
We are planning to upgrade from AIX 7.1 to AIX 7.2.
We want to know if WDI 3.3 is supported in AIX 7.2.
Is WDI 3.3 compatible with MQ 9.1 in zOS?
MQ 9.1 is the newest MQ version and the EOS for MQ v8 is April/2020.
BNSF is requesting AAR & X12 EDI 7050 standards for Websphere Data Interchange translator. The standards will be available at Washington Publishing by the middle of April, 2018. BNSF is requesting IBM to provide the EDI 7050 version for the AAR and X12 standards no later than middle of July, 2018.
I need the 7050 version of the X12 and AAR standards for the EDI transactions 161, 404, 417, 418, 419, 420, 425, 427, 440, 824, and 998. The Rail industry is requesting all railroads to upgrade the named transactions to version 7050. Railinc has s...
XSD - Max Element size (>30 characters)
We have to import multiple xsd with nested schemas, so far we have no problem.
The problem is related to the length of some elements, elements that have over then 35 characters
WDI Client 3.3 does not work Under Windows 10
WDI 3.3 Client will not load on a machine that has Windows 10. Currently getting error.
EDI 7030 standards for X12 and Rail
BNSF is requesting IBM provide AAR EDI 7030 standards for Websphere Data Interchange translator. The standards will be available at Washington Publishing by the middle of April, 2016. BNSF is requesting IBM to provide EDI 7030 standards for AAR...
Do not place IBM confidential, company confidential, or personal information into any field.