wood burning stoves 2.0*
The moose likes Websphere and the fly likes Phantom Read / Garbled Data for WAS 5 to DB2 7 OS390 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "Phantom Read / Garbled Data for WAS 5 to DB2 7 OS390" Watch "Phantom Read / Garbled Data for WAS 5 to DB2 7 OS390" New topic
Author

Phantom Read / Garbled Data for WAS 5 to DB2 7 OS390

Ed Wallen
Ranch Hand

Joined: Feb 11, 2002
Posts: 34
I experienced a problem when trying to read and write data from WAS 5 to a DB2 7 mainframe database. The data would get garbled..........so on a read, a record that existed in the database would not get found (the primary key would get garbled into a different number) and for writes, the primary key would be some integer completely out of sequence (and often negative). No exceptions were thrown, so this was hard to track down. Below are my findings.

My environment: WAS 5.0.2.7 on AIX 5.1 going to DB2 v7.1 OS/390 database through DB2Connect 8.1.5 using the JCC Universal type 2 XA driver.

IBM recommended using patch UQ84225.


Error description
DB2DDF DDFL09 DB2DRDA defect pq82641 dpq82641
Integer value is erroreously being byte reversed at Insert when
client coming in with connection pooling.
Problem summary
****************************************************************
* USERS AFFECTED: All Distributed Data Facility (DDF) users. *
* Specifically those with DB2 Connect V6 *
* (or better) client applications that are *
* using connection pooling. *
****************************************************************
* PROBLEM DESCRIPTION: Numeric values sent to a DB2/390 server *
* from a DB2 Connect V6 (or more recent) *
* client application may incorrectly be *
* thought to be in a byte reversed *
* format and DB2/390 will reverse the *
* bytes, creating an incorrect value. *
* *
****************************************************************


-Ed
Ed Wallen
Ranch Hand

Joined: Feb 11, 2002
Posts: 34
Due to this issue, some of the primary key Integers that got inserted into the database fell victim to this IBM bug. I had to provide the application team with a means of converting the identifier to the correct value (reversing the bytes). Here is the simple class that I wrote:



-Ed
[ April 01, 2005: Message edited by: Ed Wallen ]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Phantom Read / Garbled Data for WAS 5 to DB2 7 OS390