Re: Re writing CL in RPG

Charles

This reminded me of Rick Turner's documents on improving batch performance. The link is

http://www-01.ibm.com/support/docview.wss?uid=nas1e907e76673a614dd86256a290054f546

The article has links to 2 ZIP files - BATCHPFR.ZIP and BATCHPFR.FREELANCE.ZIP - the latter has Freelance presentations - you might need to get a Freelance viewer, as I don't remember whether Powerpoint will import them. The viewers are available online.

The former has a Word document that gives all manner of ways to improve batch processing. One says that just running commitment control will give a measure of journal caching - it used to be a PRPQ and is now in option 42.

A relevant paragraph is

When commitment control is in effect, the database journal write functions know that file integrity is required only at a commit boundary and not at every record update/add/delete operation. Because of this, the database journal writes are scheduled asynchronously. When a commit boundary is reached, the database functions ensure that all pending database file I/O is complete before continuing.

Lab tests show that using commitment control and journaling yields performance almost equal to not using database journaling. If you use journaling but not commitment control, a job can be three to four times slower than when you don?t use journaling at all.


Basically, one should not be afraid of journaling now - it can be quite fast, not at all as in the old days.

Regards
Vern

-------------- Original message ----------------------
From: "Charles Wilt" <charles.wilt@xxxxxxxxx>

If your TOFILE's are journalled and you don't have 5722-SS1 option 42
- HA Journal Performance installed and you're copying a significant
number of records.

Then using RPG could be significantly faster IF you open the TOFILE
under commitment control and perform a commit periodically; say every
1000 records or so.

Charles