Incremental Bind Number Wrong
MartinPacker 11000094DH Visits (1670)
If you are reporting on DB2 incremental binds, whether through DB2PE/DB2PM, some other reporter, or your own code you might find the number wrong. You know it's wrong because it plain looks silly.:-)
APAR PK16637 describes just such a problem. Note: As of today the fixes are not yet available.
The significance of this number is that it represents additional CPU cost, elapsed time, and I/Os. So getting it right is important.