Re: SQL and commitment control

[Nathan Andelin <nandelin@xxxxxxxxx>]

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