Batch Creation Timing, Rec Processing, Commit Works

[Former Member]

We have an issue where batches are created in an interface, in the same interface the created batch is then, some records later, transacted upon. In many instances this is giviing us issues because it does not seem like the batch exists. I have many commit stmts i my code, maybe too many? and on only some I include wait, then dequeue all, but not on all of them.

So I guess my question is can you have too many commit works? Create a commit counter and do every 100 recs and do all at once? Or should I have these WAIT & DEQUEUE stmts for each one. Any feedback, or suggestions is helpful.

Thank-You.

[naimesh_patel]

In General, if you are working on some kind of transaction (e.g. Order Processing), you should only one Commit Work.

Now, if you are working on the upload program which will upload some 10 Million records in your Z table than it would be better to use the Commit Work after certain records. If you try to use only one Commit for all 10 Mio records than it could run into the "Memory Page Overflow" and lead system to Bottleneck.

Regards,

Naimesh Patel