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



On 21-Feb-2012 07:37 , Jerry C. Adams wrote:
<<SNIP>>

The company that provides our Point-of-Sales applications and I
teamed up so that the stores could send an order directly to the
System i. I don't know much about the POS side, but the programmer
there said he used OLE DB to connect, which we both thought was great
because I could create an SQL DDL file on the System i into which the
orders would be dumped.

<<SNIP>>

The problem that we have been experiencing is that, occasionally, I
will get only part of the order, say 10 lines out of 100 (it varies).
I have a check at my end (the store's purchase order number) to be
sure that the store managers (not the sharpest knives in the drawer)
don't try to send the same order a second (or more) time. But on the
next cycle the rest of the order is there and, naturally, my program
rejects it as being a duplicate.

What I don't know, and have been unable to test, is whether or not
the ALCOBJ actually works if the store has already made the
connection to my bucket file when I allocate the file and start
processing. This seems to be what is happening, but is it possible? I
do know that the orders are not being submitted twice.


The connection to the server from the POS should run with isolation, and COMMIT only after all the insert activity has completed, to ensure that the processing is atomic. No more partial orders.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.