Leonard,

What you are experiencing is a common occurrance when you have TPI turned on and you are attempting to load a very large number of records into a TPI'd data set.  What is happening is that you are filling up the Transaction Manager's buffers and before the records can be posted at the check point your process has started to overwrite the previously posted transactions.  There are at least three solutions that you can utilize.  One is to disable TPI for database until you are finished loading all of the records, re-enable TPI and using the reindexing utility index the data set just loaded.  The second is to delete the indexing options for the specific data set, load the records, add the indexing options for the data set and index it.  And the third is to add the "NOXM" option to the definition of the indexed set which informs the third party  tool to bypass the Transaction Manager and post the records directly to the index sets.  As a general rule discussed in the documentation is that when you are adding a large number of transactions to a data set you should disable TPI and reindex the data sets loaded to improve the access speed when retrievals are required.  You should also reindex periodically the heavily used data sets to keep the index files "clean" to improve performance.

Tom Renz

>>> Leonard Berkowitz <[log in to unmask]> 03/24 7:50 AM >>>
We are attempting to write some 738,000 records from a flat file to an apparently
empty detail dataset that has one Image key and 7 Omnidex keys (TPI). The last
program display is 697,920 records processed. The process aborts with the following
series of error messages. The dataset now has 745,000+ entries. The dataset capacity
is 2,000,007. The EOFs of the TPI files are not even close to the LIMITs.

Thanks.

========================
Leonard S. Berkowitz
mailto:[log in to unmask] 
phone: (617) 972-9400 ext. 3250
fax:   (617) 923-5555

 73
 74 **** STALLED TRANSACTION: EXCEEDED ACCUMULATED LOG DATA THRESHOLD