AW: Non-Logged Operations on DB2/400

Are you using SQL Insert and Update Operations?
If so just try to add WITH NC (=Without Commit) at the end of the Insert or
Update statement.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Ryan Hunt
Gesendet: Monday, 19. September 2011 17:11
An: midrange-l@xxxxxxxxxxxx
Betreff: Non-Logged Operations on DB2/400

I am writing some external integration code that will be runing outside of
the AS400. It will be doing lots of data modification via native SQL
interface (over ODBC) - would prefer to avoid the QSYS.QCMDEXC interface if
possible.

I will be doing lots of data mods overnight - that do not need to be
logged - on tables that are currently journaled. I have tried the ALTER
TABLE statement with the INITIALLY NOT LOGGED option but it doesn't seem to
make a difference.

I'm looking for suggestions on how to either temporarily turn off journaling
(via SQL) on journaled tables, or perform non-logged operations (again, VIA
SQL).

I don't mind resorting to QCMDEXC if I really need to.

Thanks!