Summary of feature differences between
WebSphere Data Interchange Version v3.2.1 and Version v3.3

Content

Features and effects

For a list of features and benefits implemented with WDI v3.3,
see http://www-01.ibm.com/software/integration/wdi/features/?S_CMP=wspace

	WDI v3.3 Feature	WDI v3.3 effect	Difference would be manifest by:
1	Enhance the WDI Client to allow transaction reprocessing from the Document Store	The TSO CLIST and CICS user interface (EDIA) have been removed.	Functions to view the Event Log, process data from the Document Store (formerly called Transaction Store), and the ability to submit translations from the Client have been added in V3.3. These are features using the DB2 Workload Manage regions (WLM). As a result, some processing in CICS using PG and TX destinations (file types) are not available using Client DS processing functions.
2	The DYNSQL(Y) parameter is no longer supported with v3.3.	The use of the dynamic SQL feature of DB2 is no longer supported with the Management Reporting component. Issues with security and the inability to resolve such were a factor.	Equivalent results are obtained with DYNSQL(N).
3	LE 390 changes to enhance WDI Message Broker; upgrade to use C++ compiler	LMA processing EDI input in v3.3 validates data and produces error messages for bad data. In v3.2, LMA passed data to WDI Message Broker which failed a message containing bad data	Different error messages may appear. A problem encountered was that the print file was not showing a fatal error message in v3.3. WDI MP: Resolved by APAR IC64243 (SFP4) WDI z/OS: Resolved by APAR PM01009 (PTF UK52025)
4	WDI Message table was converted from MSGX parts to XML syntax, internal enhancement for maintainability	Message table change resulted in reformatting message text used as input to the DB2 Message Table	Some multi-line messages in the WDI Print File will have the same content but be formatted differently. Some single line messages might have spacing differences between parameters and message text.
5	Internationalize product for Unicode use	Acknowledgment Map names use $ rather than &; Byte order mark in v3.2.1 gets UP0021, but does not fail in v3.3	Distributed object names and profiles will have name changes; Correctly process BOM
6	Replace third-party software product Crystal Reports as a reporting tool	Crystal Reports was replaced as a reporting tool by HTML	Some differences in the way reports generated from the client are formatted
7	Enhance TRANSFORM command	Keywords on TRANSFORM command are now edited for validity against of all available Keywords. Editing is still not command specific.	Invalid keywords on the TRANSFORM command will cause the command to fail without processing, e.g. RECIDLEN(35) RECIDTBL(P719-1)
8	Ability to assign a different recordidinfo record to each ADF Record, thus allowing multiple record ids in an ADF. In v3.2.1, a single recordidinfo was assigned to all records in the ADF, with a fixed position	v3.3 determines the appropriate recordidinfo record to be used and assigns a default recordidinfo record if one is not found. WDI now requires that Application Data match the appropriate Data Format Record definition, especially when 'no delimiters' is specified on the Data Format General Tab. The UP0021 message will identify data that is not the proper length and will issue a return code of 8.	PMR 04551,999,756 In v3.2.1, bad data fails with a UP0021; with v3.3, an attempt is made to process the data. WDI MP: Resolved by APAR IC65355 (SFP4) WDI z/OS: Resolved by APAR PM08390 (PTF UK54622).
9	Enhance information in print file	Additional messages appear in the Print File to identify input data objects used and to identify output queues.	V3.3 print file has now contains FF0007 informational messages.
10	Envelope enhancements	Improve envelope usage, modify envelope attribute defaults	Found problem with UNTDI enveloping. Resolved with APAR PM07292

Differences in Messages between WDI 3.2 and WDI 3.3

This section summarizes differences in WebSphere Data Interchange (WDI) that have occurred with the release of WDI v3.3.

For I. Differences in Message Text, comparisons were made between the WDI v3.2 msgs.ixf file and the WDI v3.3 msgs.del file.
The comparisons were made after extracting the needed message parts (Message ID and text) to new files and using a Comparison tool
(in this case , Beyond Compare) to identify the differences.

For II. Differences in Message Severity, comparisons were made without the use of a comparison tool due to the layout of the
WDI 3.2 messages file.
Documentation discrepancies are also listed in this section.

Differences in message occurrences were noted from test case executions.


I. Differences in message Text:

The following types of differences have been identified between WDI 3.2 and WDI 3.3 message texts.
The specific messages and the differences are noted in supplemental spreadsheet,
“Differences between WDI 3.2 and WDI 3.3 Messages”.

	Difference in Message Text	Examples
1	Extra space in message in WDI 3.3.	3.2 - "AM0005 An error occurred while parsing the XML document. Message text from parser is: &1&2&3&4&5" 3.3 - "AM0005 An error occurred while parsing the XML document. Message text from parser is: &1&2&3&4&5"
2	One less space in message in WDI 3.3.	3.2 - "TPP208 Acknowledgment transaction ID : &01" 3.3 - "TPP208 Acknowledgment transaction ID : &01"
3	Message text changed. The words within the message have been changed. This can include changes in word spelling, the addition or removal of words within the message text and/or rewording of message text.	Text changed. 3.2 - "CR0320 EDIQ transaction failed, problem with MQPROF specification in MQSeries TRIGDATA field" 3.3 - "CR0320 EDIQ transaction failed, problem with MQPROF specification in WebSphere MQ TRIGDATA field" Text changed. 3.2 - "EV0011 Database transaction failed. SQLCODE = &1." changed to 3.3 - "EV0011 Database transaction failed. Function=&1, SQL code=&2, Table=&3." Text changed. 3.2 - EV0020 - spelling of the word "preceeding" changed to "preceding" in 3.3 and extra space in 3.3 message. Text changed - 3.2 - "RS0001 - a VSAM error during a(n) &1 operation on DDNAME &2." changed to 3.3 - "RS0001 - an error during a(n) &1 operation on &2.".
4	New message with WDI 3.3.	"EV0006 No plugin accepted the message during de-enveloping. Condition detected in method &1." "TS0510 Functional acknowledgment is overdue. User Code= &1. Transaction Handle= &2. Nickname= &3. Receiver ID= &4."

II. Differences in Message Severity:

The following have been identified as differences between WDI 3.2 and WDI 3.3 message severities:

Message EV0011 was incorrectly marked in the Messages and Codes manual as Severity 4 in WDI 3.2, but was actually
issued in Print Files with Severity 12.
It is marked in the Messages and Codes correctly in WDI 3.3 and is still issued with Severity 12.

	Message ID	Difference in Message Severity
1	EV0011	Message EV0011 was incorrectly marked in the Messages and Codes manual as Severity 4 in WDI 3.2, but was actually issued in Print Files with Severity 12. It is marked in the Messages and Codes correctly in WDI 3.3 and is still issued with Severity 12.
2	MQ0003	Message MQ0003 originally was issuing Severity 8 in WDI 3.2, but was changed to issue Severity 12 in WDI 3.2 Change implemented with PTR 8010752. It is still marked incorrectly in the Messages and Codes in WDI 3.3, but is issuing a Severity 12 in WDI 3.3. Ref: IC49378 / PK29510 / P8010752.
		Some WDI 3.3 Messages and Codes Guide documentation problems to be addressed by PTR 8012092:
3	TM0051	TM0051 Table entry &1 already exists Severity: The Severity value is missing. It should be a value of "8".
4	TM0090	TM0090 Cannot display panel &1 Severity: 1 The Severity value is "1". It should be a value of "12".
5	TS0310	TS0310 Internal error updating transaction store: &1. Severity: 12 The Severity value is "12". It should be a value of "8".
6	VA0003	VA0003 An attempt to validate a message failed. The message's syntax was &1. Severity: 12 The Severity value is "12". It should be a value of "8".

III. Differences in Message Occurrence:

This section may have updates as further code changes in WDI 3.3 affect message occurrence changes.
The following have been identified as differences between WDI 3.2 and WDI 3.3 message occurrences:

1) As a result of PTR 8012069 (APAR PM08390) –
There is a change with respect to data handling. Data that may not have generated errors prior to this change may now generate
UP0021 and EV0003 errors.
We have seen tests fail in several environments. These have been caused by incorrect delimiters defined in the ADF, incorrect
character length definitions in the ADF, and individual records that describe too little of the actual data. Records that include binary
fields that are defined at the end of the record may cause additional errors.


IV. References/Supplemental Documentation:

A) msgs.del - located in the ddl subdirectory of the WDI 3.3 install directory, a list of messages no longer in WDI in internal WDI format. Use Wordpad to view this list in a formatted manner.
B) msgs.ixf - located in the ixf subdirectory of the WDI 3.2 install directory. A list of deleted messages in DB2 load data format. Use Wordpad to view this list in a formatted manner.
C) attachments