RE: RUNSQL behavior difference with STRSQL -- MIDRANGE-L

Subject: RE: RUNSQL behavior difference with STRSQL
From: Rob Berendt <rob@xxxxxxxxx>
Date: Mon, 29 Jan 2018 08:38:04 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

But the real question is: Do you know why that did the trick?

Here's why: When you do operations with commitment control it uses the
journals and their receivers to record transactions. And if you do a
ROLLBACK it will use RMVJRNCHG. If you are not using journalling it's
impossible to use commitment control. And it's not kosher to set up
journals on items in QTEMP.

Rob Berendt

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.