Re: Commitment control

[rob@xxxxxxxxx]

A trigger on the file.  When the "last record" comes in, then initiate the 
poll.  Or update a data area.  The remote system would poll that data 
area.  When it says it's ready to rock then retrieve the file.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





ouuch@xxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/21/2003 02:20 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Commitment control


Hi,

well, we have a shipment notification file, which is regularly polled for 
new shipments by a 
remote location. A shipment can consist of lots of records, so we need to 
make sure that 
remote gets all records and not only 99 because the last record hasn't 
been written yet.

A colleague came up with the idea to use commitment control here (we have 
never worked with 
it before):

             - start commit cycle
             - write xxx records
             - commit

He believes all xxx records will only get visible in the file when the 
commit is issued. Is this 
true?

I suggested to have a last-line flag and a logical only showing records 
with that flag active. 
Remote can poll the logical and when it finds the last record, then read 
from the physical file 
with the appropriate key.

Any other solutions for this problem?

Regards,

Oliver
_______________________________________________
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.