I have an update for everyone considering an upgrade to v5r3. In a 
nutshell, we have a Domino server at v5r2 and another non-Domino 
production server at v5r3 (we upgraded it from v5r2 this past weekend). 
After the upgrade of the production server to v5r3 our SQL code running 
from the Domino box to the production box began failing.

Actually, it was running correctly but it was not returning all the data. 
According to APAR SE16786, "The SQLCA was changed at R530. Some clients 
may read the change to report SQL0100 - Row not Found when the row is 
really returned to the client." What we experienced was that the client 
(Domino) was receiving x-1 rows. If we were supposed to get 9 records we 
got 8. If 1, then we got zero.

The solution to this APAR was a TEST PTF from IBM - SI15099. After ending 
some server jobs and applying that fix, our code began to run normally 
again.

Chris Whisonant
Comporium
Senior Mid-Range Systems Administrator
IBM eServer Certified Systems Expert - iSeries Technical Solutions V5R2
IBM Certified Associate System Administrator - Lotus Notes and Domino 6
803.326.7270 | 803.326.6142 fax

domino400-bounces+chris.whisonant=comporium.com@xxxxxxxxxxxx wrote on 
10/25/2004 02:33:23 PM:

> No clue.  But I have found some 'interesting' things about DB2 on V5R3. 
> 
> I couldn't find a reference to 664 in either SQLCOD or SQLSTT at
> http://publib.boulder.ibm.
> com/infocenter/iseries/v5r3/ic2924/info/rzala/rzalafinder.htm
> 
> Didn't see anything pertinent here either
> http://www.lotus.com/ldd/communities.nsf
> 
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
> 
> 
> 
> 
> 
> Chris Whisonant <Chris.Whisonant@xxxxxxxxxxxxx> 
> Sent by: domino400-bounces+rob=dekko.com@xxxxxxxxxxxx
> 10/25/2004 12:15 PM
> Please respond to
> Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
> 
> 
> To
> Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
> cc
> 
> Fax to
> 
> Subject
> SLQ After Upgrade
> 
> 
> 
> 
> 
> 
> Upgraded our main iSeries from 5.2 to 5.3 yesterday. Our Domino iSeries 
is 
> 
> still at 5.2. We have a workflow application that is not fully updating 
> records using the SQL code. It's just a basic SQL UPDATE procedure that 
> modifies a field.
> 
> It appears that it's updating the main iSeries data but we're getting an 

> SQL error 664 and it's not updating the Notes records properly.
> 
> Anyone have any ideas as to why an upgrade to 5.3 would cause this to 
> fail?
> 
> Chris Whisonant
> Comporium
> Senior Mid-Range Systems Administrator
> IBM eServer Certified Systems Expert - iSeries Technical Solutions V5R2
> IBM Certified Associate System Administrator - Lotus Notes and Domino 6
> 803.326.7270 | 803.326.6142 fax
> _______________________________________________
> This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
> To post a message email: Domino400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/domino400
> or email: Domino400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/domino400.
> 
> 
> _______________________________________________
> This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
> To post a message email: Domino400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/domino400
> or email: Domino400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/domino400.
> 

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.