Re: ODBC PTF Defect

Found out the source of this "defect."  It turns out, we were taking
advantage of a bug in the ODBC drive that allowed the MS jet engine to
see non-unique indexed files as unique indexed files.  The MS products
(which use a common jet engine) demand a unique key for updates.  So I
guess one person's "bug" is another's "interface" . . . 



Jeffrey M. Carey wrote:
> 
> We recently came across a problem with the ODBC PTF's on both V3R2 and
> V3R7 (presumably on V3R1 as well, but haven't tested that).
> In V3R2, PTF SF38338 (on cume 7126) and its superceed SF41227 cause this
> problem with ODBC - when trying to update an AS/400 table, the operation
> will fail unless the logical over the file has a UNIQUE key.
> Previously, we could update with a non-unique key (which should be the
> case, as AS/400 SQL allows updates top tables with non-unique keys).
> We found the same problem on our V3R7 system (which is at cume 7161),
> but not on our V3R1 system (which is still back at 7044).
> To get around this until a fix is developed, we had to remove SF41227
> (note that removing SF38338 wasn't enough - we removed that, then
> applied SF41227 and a few other PTF's IBM recommended, then removed
> SF41227).
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *