Re: Object Allocation Problem - or Something Else?

[Charles Wilt <charles.wilt@xxxxxxxxx>]

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.