LOGCACHEDELAY

Specifies the delay in seconds that will be imposed before any newly scraped Db2® log data is added to the InfoSphere® CDC Log Cache, unless the newly scraped Db2 log data fills a complete InfoSphere CDC Log Cache buffer (whose size is determined by the CACHEBLOCKSIZE keyword).

During periods of low to moderate Db2 log volume, continually writing small amounts of log data to the InfoSphere CDC Log Cache and then forcing each subscription to read those small amounts of log data, can cause CPU consumption by InfoSphere CDC for z/OS® to become very high. Reducing the rate of reads and writes to the InfoSphere CDC Log Cache by imposing a small delay can drastically reduce CPU consumption. The price paid for this reduction in CPU consumption is that if Db2 log volume is very low, latency can increase by as much the delay imposed. If the Db2 log volume is very high, then the InfoSphere CDC Log Cache buffers fill so quickly that the delay no longer controls when the buffers are written to the InfoSphere CDC Log Cache, since the buffers are always written when they are full. Therefore, when the Db2 log volume is very high, the delay has little or no effect. Where CPU consumption has become a problem, delays of 2 to 5 seconds should be sufficient.

If a fractional value is specified, the period (.) character must be used as the decimal point, regardless of your locale. If the comma (,) character is used, the parser interprets the comma as the end of the value. InfoSphere CDC will replace the period character with the correct decimal point for your locale before converting the text to a numeric value. Only the first two digits after the decimal point are significant.

This keyword is optional.

Default Setting—0

Minimum (Non-Zero) Setting—0.01

Maximum Setting—999.99