|
Folks: I've encountered a particularly perplexing problem with JDBC. I'm using a fairly recent version of the open source JT400 to do some JDBC access. The database operations are quite simple, just insert some records into a file on the 400. When I run the JDBC operations on a V4R3 system (our development box), it works fine. When I run the same operation on a V4R4 system (testing box), the first record is added fine ... but when the second record is added, I get a SQL7008 message with reason code 3. Reason code 3 indicates that the file is not journaled. Well, that's true ... it isn't journaled. On either system. My search of previous messages in the archives indicate that a file updated by JDBC needs to be journaled. But my experience shows this is not true. We have a number of files that are updated by JDBC without a problem, and we never journal files. The JDBC URL we're using is "jdbc:as400://system.domain.com/LIBRARY;naming=system;errors=full" Any suggestions? Thanks! david -- David Gibbs Sr. Software Engineer MKS, Inc. 2500 S. Highland Ave, Suite 200 Lombard, IL 60148 (630) 495-2108 x5004 Need a laugh (we all do these days): visit http://www.userfriendly.org
As an Amazon Associate we earn from qualifying purchases.
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.