|
If you've recently installed iSeries Access (V5R3) on your PC, the new default for the ODBC driver's "Commit Mode" is Read Uncommitted (*CHG). This requires that your files be journaled for most operations (except read, I think). To change the default, go into the configured driver, select the "Server" tab, go into the Advanced options and set the "Commit Mode" to Commit Immediate (*NONE). Thanks, >>> Jeff.Glenn@xxxxxxxxxxxxxxxxxxx 03/14/05 02:17PM >>> Hello. Has anyone had this problem? We're using Access to update a file on a V5R3 machine. We get the error "ODBC--update on a linked table 'xxxx_xxxx' failed. SQL7008 - xxxx in xxxx not valid for operation. (#-7008)" that seems to be common. >From what I understand from the archives, this typically means that the ODBC setting is expecting commitment control and the file is not being journaled. However, the ODBC setting for Commit mode is Commit immediate (*NONE). If we start journaling the file, the update works correctly. Why is the ODBC connection ignoring the Commit immediate setting? I'd rather not journal the files we're updating. Thanks, Jeff -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.