IBM Support

WebSphere Data Interchange Version 3.3 Server Fix Pack downloads

Product Documentation


Abstract

This document provides links to Server Fix Pack downloads for WebSphere Data Interchange Version 3.3. Downloads are listed from the most recent to the oldest.. These Server Fix Packs contain the latest set of problem resolutions. Server Fix Packs are cumulative and contain all previous fixes in the latest one. Read the readme file for additional instructions and full details and list of resolved problems.

Content

June 25, 2021
WebSphere Data Interchange v3.3 Server Fix Pack 13 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.
Note: There are no client dependencies for this Fix Pack, but it is suggested to always run with the latest Client Fix Pack for full functionality.
Note:  Additional testing completed using  AIX 7.2, DB2 11.5.
June 30, 2017
WebSphere Data Interchange v3.3 Server Fix Pack 12 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: This Fix Pack includes the X12 Functional Acknowledgment map for support of the ST03 element implemented in X12V4R6. This element has been available with Data Transformation mapping, and this change implements this feature with Receive maps. WDI Client Fix Pack 15 is required to specify this FA map in the Receive map usage.
 

June 2, 2016
WebSphere Data Interchange v3.3 Server Fix Pack 11 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: There are no client dependencies for this Fix Pack, but it is suggested to always run with the latest Client Fix Pack for full functionality.

Note: This update includes a performance change to the DB2 definitions for Management Reporting tables. Clients who use the Trading Partner Capability Report will want to apply "sfp11.ddl" following the directions in the "readme.txt" before using the revised report.
   

July 11,, 2014
WebSphere Data Interchange v3.3 Server Fix Pack 10 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: There are no client dependencies for this Fix Pack, but it is suggested to always run with the latest Client Fix Pack for full functionality.

Note: This Fix Pack contains a revision to the Management Reporting feature that may cause growth in
the DB2 tables used to accumulate activity history. If this might impact your implementation, please carefully
review the materials for APAR PI13317 including this Technical Document.
 

February 15, 2013
WebSphere Data Interchange v3.3 Server Fix Pack 9 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: There are no client dependencies for this Fix Pack, but it is suggested to always run with the latest Client Fix Pack for full functionality.  
October 15, 2012
WebSphere Data Interchange v3.3 Server Fix Pack 8 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: There are no client dependencies for this Fix Pack, but it is suggested to always run with the latest Client Fix Pack for full functionality.  

April 20, 2012 - revised
March 30, 2012 - Original GA date
WebSphere Data Interchange v3.3 Server Fix Pack 7 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: To take full advantage of the enhancements and fixes we recommend that you also have the latest Client Fixpack installed.

1) WDI v3.3 Client Fix Pack 13 is referenced by APAR PM48907, included in Server Fix Pack 7 and associated with PTF UK73341. If PTF UK73341 is applied, then Client Fix Pack 13 should be applied to complete the restoration of the Log EDI function.

2) Revision - April 20, 2012
SFP7 was released March 30, and a WDIServer (WDI Advanced Adapter) error
was found in the release. It is resolved with APAR IC82588.
If SFP7 was downloaded before April 16, it is recommended that the revised
SFP7 package be downloaded again and re-installed.
The build date of the original SFP7 is March 27, 2012,
The build date of the revised SFP7 is April 16, 2012.

3) P8012232 - IC81513
One of the changes in APAR IC71573 (P8012161) in SFP5 changed behavior about
which transactions are sent to the WMQ failure queue.
This APAR reverses that behavior.

Clients upgrading to SFP7 who make use of the WebSphere MQ "Advanced Adapter"
should verify that SFP7 exception processing continues to support their message
flow.

The wdi.properties parameters "rollback", "genprtfile", and "userexitname"
customize much of the processing. The "rollback" property defaults to "no"
so an individual WMQ message will not be replaced on the queue for subsequent
backout processing. Whereas rollback=yes can be used to reprocess failed messages
as many times as defined for the queue definition setting "Backout threshold."
The "genprtfile" continues to default to "onerror" and may be changed to "always"
or "never." For "always" and "onerror" values, WDI writes a message to the
"WDI.PRTFILE.Q" containing the Audit Log and an additional message reporting the
routing to the failure queue (WDI.FAILURE.Q) or the BOQNAME from the triggering
WMQ Queue. The reporting messages start with text like
"Message 414d51207764695f6d616e616765722072338b4f2002b205 failed translation"
followed by a few words of description. WDIService routes to the failure queue
based on translation return codes that may be customized through the "userexitname"
dynamic library as distributed in samples. Absent such an exit, WDIService stops
processing for system errors, return code 12 or higher, and some translation errors
- return code 8 where the extended return code is greater than 31.
Other extended return code values will rollback, if allowed, or route directly to
the failure queue. The values "1" and "2" may indicate successful translation or
failure based on "Acceptable error level" settings as defined in the Map rule or
Usage.

See a TechNote explanation about wdi.properties parameters in
http://www-01.ibm.com/support/docview.wss?uid=swg21498562.  

August 5, 2011 - Revised
July 15, 2011 - Revised
June 30, 2011 - Original GA date
WebSphere Data Interchange v3.3 Server Fix Pack 6 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: To take full advantage of the enhancements and fixes we recommend that you also have the latest Client Fixpack installed.

This SFP will also work with earlier versions of the WDI 3.3.0 Client, but at a reduced level of function.
APAR PM18749 fixed in WDI 3.3 Server Fix Pack 5 is dependent upon Client Fix Pack 11. That is, when applying Server Fix Pack 5, multiple DB2 views will be changed, for which Client Fix Pack 11 is
required for proper functionality. If the DB2 views are changed accordingly, and CFP11 is not yet deployed on user's WDI Client, the following error will result when entering a partial Transaction Handle value on
the Selection Criteria window for the "Transactions" or "Enveloped Transactions" tab:
11041: A database error occurred while attempting to open table "EDIENU33.EDIVTSTH". ODBC return code is -1.
Description: SQL0181N The string representation of datetime value is out of range. SQLSTATE=22007.

On the other hand, Client Fix Pack 11 may be installed without first applying Server Fix Pack 5 or 6, however, the user will not gain improved performance without the new DB2 view therein. See the following link for apar PM18749 details: http://www-01.ibm.com/support/docview.wss?uid=swg1PM18749
 
Revision - July 15, 2011
SFP6 was released June 30, and two errors where found in the release. They are resolved with APARs IC77318 and PM43273.
If SFP6 was downloaded before July 7, it is recommended that the revised SFP6 package be downloaded again and re-installed. The build date of the original SFP6 is June 24, 2011, The build date of the revised SFP6 is July 8, 2011.
Revision - August 5, 2011
SFP6 was refreshed on August 5, 2011. The sfp6.ddl and sfp5.ddl files were added to the AIX download package.
 

January 25, 2011 - revised
November 30, 2010 - original GA date
WebSphere Data Interchange v3.3 Server Fix Pack 5 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: To take full advantage of the enhancements and fixes we recommend that you also have the latest Client Fixpack installed.

This SFP will also work with earlier versions of the WDI 3.3.0 Client, but at a reduced level of function.
APAR PM18749 fixed in this WDI 3.3 Server Fix Pack is dependent upon Client Fix Pack 11. That is, when applying Server Fix Pack 5, multiple DB2 views will be changed, for which Client Fix Pack 11 is
required for proper functionality. If the DB2 views are changed accordingly, and CFP11 is not yet deployed on user's WDI Client, the following error will result when entering a partial Transaction Handle value on
the Selection Criteria window for the "Transactions" or "Enveloped Transactions" tab:
11041: A database error occurred while attempting to open table "EDIENU33.EDIVTSTH". ODBC return code is -1.
Description: SQL0181N The string representation of datetime value is out of range. SQLSTATE=22007.

On the other hand, Client Fix Pack 11 may be installed without first applying Server Fix Pack 5, however, the user will not gain improved performance without the new DB2 view therein. See the following link for apar PM18749 details: http://www-01.ibm.com/support/docview.wss?uid=swg1PM18749
 
Revision - January 25, 2011
SFP5 was released without the sfp5.ddl file in the install package. To access the ddl statements required,
download the spf5.ddl file and place the file in the ddl folder within the Installation folder,
e.g. Program Files -> IBM -> WDIServer -> V3.3 -> ddl
Then follow the database change instructions in the SFP5 readme.txt
April 19, 2010
WebSphere Data Interchange v3.3 Server Fix Pack 4 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: There are no client dependencies for this Fix Pack, but it is suggested to always run with the latest Client Fix Pack for full functionality.
  December 18, 2009
WebSphere Data Interchange v3.3 Server Fix Pack 3 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: There are no client dependencies for this Fix Pack, but it is suggested to always run with the latest Client Fix Pack for full functionality.
  May 12, 2009
WebSphere Data Interchange v3.3 Server Fix Pack 2 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: There are no client dependencies for this Fix Pack, but it is suggested to always run with the latest Client Fix Pack for full functionality.
  April 30, 2008
WebSphere Data Interchange v3.3 Server Fix Pack 1 is now available.
Please read the Readme file first and carefully for full details prior to installing the Fixpack.

Note: There are no client dependencies for this Fix Pack, but it is suggested to always run with the latest Client Fix Pack for full functionality.
 


Instructions:
  1. Select a version and click on the Server Fix Pack file listed above to download.
  2. Please download the applicable readme.txt file above and follow the installation instructions specific to the platform you have selected.

Please contact IBM support if you have problems installing this product.

[{"Product":{"code":"SSFKTZ","label":"WebSphere Data Interchange"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"WDI 3.3 MP","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF025","label":"Platform Independent"},{"code":"PF033","label":"Windows"}],"Version":"3.3","Edition":"All Editions","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
20 April 2023

UID

swg27010382

Page Feedback