Re: SQL and commitment control -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: SQL and commitment control
From: Sam_L <lennon_s_j@xxxxxxxxxxx>
Date: Wed, 1 Jan 2020 14:15:24 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

It may depend on how the interactive SQL is started,
Does STRSQL COMMIT(*CS) make any difference?

Sam

On 1/1/2020 12:31 PM, smith5646midrange@xxxxxxxxx wrote:

I have an RPGLE program that I adding commitment control. When I insert
records to my file but have not yet committed them, I can go to a second
session and using interactive SQL, I can see them. When I do a rollback in
the program, they disappear (as I would expect).

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: SQL and commitment control , smith5646midrange

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.