This is the same as any connection, even straight JDBC.If the connection runs in an isolation level, the tables must be journalled.You need to connect using *NONE or better journal the library and the file there.
On Thursday, February 12, 2026 at 04:33:10 PM GMT+1, Patrik Schindler <poc@xxxxxxxxxx> wrote:
Hello Stephen,
Am 12.02.2026 um 16:25 schrieb Stephen Landess <steve_landess@xxxxxxxxxxx>:
It appears that when using the IBMDASQL OLE DB driver that the tables on the IBM i system are read-only unless they are either journaled or located in a collection (which by default, are journaled).
I remember a similar issue with plain ODBC. If tables are journaled and you fail to set commitment mode to *NONE, an automatic rollback will discard all your changes, and it appears that the tables are read-only without any warning message.
Maybe this is related? Can you influence the commit mode with OLE? I'm not a Windows user, so I have no idea about this. But if there is a way to set commitment mode to *NONE, I presume, changes should be written back to the tables immediately.
:wq! PoC
This mailing list archive is Copyright 1997-2026 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.
midrange.com
