× 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.



Sorry, I should have been a little clearer on the reasoning. The program is
using a multi header / detail group of files and I am inserting / updating
records that the user may decide they don't want to keep. I don't want
other programs seeing / using the records for anything until they are
committed.

To give an (unrelated) example of why I want to do this...assume someone is
creating a PO with header, details (linked to header), comments (linked to
details), etc. While it is being created, if someone runs a report and only
the header has been written the report may abend without detail records (I
know, badly coded report but bear with me). Another possibility is someone
runs a program to determine outstanding liability to vendors and it picks up
this new PO even though the user decides to not save it. Now the vendor
liability is overstated and nobody has a clue what happened because the new
PO was rolled back and doesn't exist anywhere.



-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Nathan
Andelin
Sent: Wednesday, January 1, 2020 1:14 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: SQL and commitment control

In regard to hiding database updates from other sessions, that seems like a
very unorthodox, perhaps even heretical behavior for a shared database. The
only way I can think of doing that would be to create a table in your
session's qtemp library.


On Wed, Jan 1, 2020 at 10:31 AM <smith5646midrange@xxxxxxxxx> wrote:

I feel like I know the answer to this but I'm missing something and
can't figure it out.



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). The
part that I'm drawing a blank on is I thought there was a way to
prevent the other sessions from seeing the records until they were
committed. Am I remembering incorrectly?
I've tried commit = *chg and *cs but neither hide the records from the
other sessions. What am I missing? And feel free to ask basic
questions because assuming this is possible, I am obviously missing
something basic.





--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.