I think that's a good lead. Most AS/400 tables are not journalled and do not support transactions. Try using the EXTERNAL transaction manager which will turn off all transaction processing in iBATIS - maybe it will make a difference.
BTW - the AS/400 terms for transactions are "commitment control" and "journalling". Ask the AS/400 folks in your shop if they've these things - my guess is probably not.
Jeff Butler
On 2/24/06, Eric Blue <[EMAIL PROTECTED]> wrote:
Hi Davis,
Do you have autocommit enabled by default? Trying Googleing 'db2 "not valid for operation"'. I noticed quite a few references to an error message like this due to journaling/commit/rollback problems.
On 2/24/06, Davis Chapman <[EMAIL PROTECTED] > wrote:I'm running into a perplexing problem. I'm trying to replace a homegrown DOA
with iBatis in an application running against DB2 on an AS/400. All of my
selects are running fine. But when I try to run an Insert statement, I get
the following error:
Caused by: java.sql.SQLException: [SQL7008] ECEP in T0MD618D not valid for
operation.
Caused by: com.ibatis.common.jdbc.exception.NestedSQLException :
I've double checked everything I can think of. I'm connecting with the
correct credentials, etc. I've used iBatis extensively in other projects
with lots of success, but this has me baffled. Any ideas what could be
wrong?
Thanks,
Davis Chapman
