Hi HVR Support,

After upgrading our HVR Hub from version 6.2 to 6.3, we observed additional DB2 for i journal receiver scanning messages in the Capture logs that were not present in HVR 6.2.

Examples:

Scanned Db2 for i Journal Receiver

Scanned Db2 for i Journal Receiver 'JRNRCVLIB/LTU4242188' sequence number '5328015908' - '5328016314'

We understand these messages are related to the journal receiver scanning changes/improvements in HVR 6.3.

These additional log entries are generating increased log information and additional storage consumption on the HVR Hub.

We would like to understand the following:

1. Are these DB2 for i journal receiver scan messages required for normal production operation?
2. Is there a supported environment variable or configuration option to disable or reduce these messages?
3. If they can be disabled/reduced, what is the recommended setting and would there be any impact to Capture or replication?

We are also investigating CPU utilization on the DB2 for i Capture sites. HVR Support previously recommended HVR_SCAN_POLL=5 and HVR_TIME_PROFILER_TRACE=MEDIUM for CPU analysis.

We would like guidance on:

4. How can we use HVR_TIME_PROFILER_TRACE to identify the CPU time consumed by HVR Capture?
5. Which entries or metrics in the trace/log should be reviewed?
6. Is there a recommended way to compare CPU usage before and after changing HVR_SCAN_POLL?
7. Does enabling the time profiler generate additional logs or storage overhead, and how should it be disabled after troubleshooting?

Since these observations started around the HVR 6.3 upgrade, we would like to understand what logging/profiling behavior is new in HVR 6.3 and what can safely be controlled in a production environment.

Please provide the recommended configuration and best practices.

Thanks,
Satya