My program, which processes the file, is simply RPG IV; no SQL in it. I
meant that, when I created the DTOORDERS table, I used DDL and ran RUNSQLSTM
with COMMIT(*NONE).
Commitment control is, admittedly, one of the things I have *never* used so
I may be confusing both of us. Anyway, I thought that, if the table was
created with COMMIT(other than *None), that the program had to use COMMIT to
actually add/update/delete the records/transactions.
And, if the table was created with COMMIT(*None) that you couldn't use
COMMIT in the program (or that it wouldn't have any effect, at least).
Guess I'll have to do some reading when I get back to work on Thursday
because this is sounding like the way to go. Plus get with the POS [Thanks,
Jeff, it does fit] vendor.
Youse guys are making my day. Really.
Jerry C. Adams
IBM i Programmer/Analyst
When two men agree on everything, one is unnecessary. -Sign in Philip
Wrigley's office
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Tuesday, February 21, 2012 1:14 PM
To: Midrange Systems Technical Discussion
Subject: Re: Object Allocation Problem - or Something Else?
Not sure what you mean...
Creating a table with COMMIT(*NONE) or COMMIT(*CS) makes no sense...
Do you mean you created the SQLRPGLE program that reads the data with
COMMIT(*NONE)?
Then yes, you'd need to change it to COMMIT(*CS).
But the POS side will also need to being inserting all the records as a
single transaction. As it is, by default it is probably auto-commiting
after each record.
Charles
On Tue, Feb 21, 2012 at 1:43 PM, Jerry C. Adams <midrange@xxxxxxxx> wrote:
All of this stuff about commitment control reminds me that I created
the file with COMMIT(*NONE). So, would changing the file to
COMMIT(*CS) and then changing my program, which reads the file and
deletes records it used, to COMMIT the deletes be sufficient, or would
the vendor, also, need to use COMMIT? Sounds like belt and suspenders,
but no harm in that.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
