Smart/RRSAF COMMIT_DB2_CHANGES commit pacing option does not trigger commit as expected

Products

• Smart RRSAF

Issue/Introduction

Smart/RRSAF COMMIT_DB2_CHANGES pacing option does not trigger a commit when in a Db2 attach only mode.

Scenario: 
Simple program which performs fetch row and insert row to Db2 table.
Tablespace with attributes LOCKMAX 0 and LOCKSIZE ROW along with DSNZPARM NUMLKUS 10000.

Smart/RRSAF commit pacing options:
COMMIT_TIME(0500)                
COMMIT_DB2_CHANGES(1000)

   
Expected result would be commits every 1000 inserts but actual result abend at 10000 due to MAXLOCK 00C90096.
DB2 attachment is RRSAF.

Resolution

No physical commit is initiated by Smart/RRSAF without a logical commit request from the application to trigger it.
A Db2 logical commit request from the application is suppressed until one of the Smart/RRSAF commit pacing conditions are satisfied.

The following Smart/RRSAF commit pacing parameters can be used in combination to control application commit pacing:

COMMIT_PACE 
COMMIT_Db2
COMMIT_Db2_CHANGES
COMMIT_TIME

** Setting COMMIT_PACE(1) will have the effect of honoring any native SQL commit 
** Smart/RRSAF Profile Defaults may be in effect if a commit pacing option is not specified