Re: Commitment control

> Oliver wrote:
> 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.

Oliver -

Do you have the source code for the program(s), and are you willing to
modify your code to handle this?

We have a system that works similarly to what you are trying to do.  Our
solution was to use a separate file to drive the remote process.

We have order detail transactions that need to be sent to a downstream
system via an EAI (Enterprise Application Integration) package that use ODBC
to monitor files on the iSeries.  When a record appears, the EAI script
starts running.  Like you, we don't want the transactions sent until all of
the detail records have been created in the order detail file.

We have a separate file that drives the outbound sending process.  When all
detail records have been created (or changed), the RPG program creates a
record in this file with the necessary key information to process the detail
records just created or changed in the order detail file.  The EAI script
monitors _this_ file and creates an XML document to send to the downstream
system.

For example:

You are creating shipping transactions in a file named SHPDTL, which has the
shipment detail information.
Create a new file named SHPRDY that has all of the necessary key fields to
retrieve the necessary detail records from the SHPDTL file.

After you have created all of the details in SHPDTL, write a record to
SHPRDY.

Have the remote process monitor the SHPRDY file.  When it sees a record
appear in SHPRDY, it uses the key information from SHPRDY to read thru the
SHPDTL records and pick up the data it needs, then either deletes the SHPRDY
record or flags the SHPRDY record as having been processed.

HTH,
Steve Landess
Austin, Texas
(512) 423-0935