Rows per commit

rupeshg · Post by **rupeshg** » Mon Oct 06, 2008 5:50 am

Hi

Commit frequency in Job properties is related to the number of rows it processes. Meaning, if the values is 100, it will commit after 100th record is loaded successfully on the target table.

This should be true for one output link to one target. What happens if the input is one and output links are multiple? Here, one input row is split into multiple rows, may be from a transformer going into different tables. Now, how are the rows counted for commit to happen? Is it counted at source or at output? Assuming the counting is at the output, does it take output links into consideration where one input row is split into multiple rows?

I hope the explanation is understandable.

Regards
Rupesh

Mike · Post by **Mike** » Mon Oct 06, 2008 6:16 am

Hi Rupesh,

It's been way too long since I've done anything with mainframe jobs, so I don't remember the answer to your query.

Investigate the generated COBOL. It is very readable code, so you will be able to find your answer easily.

Mike

chulett · Post by **chulett** » Mon Oct 06, 2008 7:14 am

I can't imagine this is different in mainfraime jobs but transaction size is a link property everywhere else. That is, each output link will check the number of rows down it and commit as needed.

Mike · Post by **Mike** » Mon Oct 06, 2008 7:47 am

Mainframe jobs are quite a different animal. It actually is a job property. No link-level control

. I'm guessing it's a global counter in a mainframe job, but don't have any generated code to verify.

Mike

chulett · Post by **chulett** » Mon Oct 06, 2008 7:49 am

Interesting.