2149245 - sp_monitorconfig report for max_used 'number of locks' may be inaccurate show decreased value - SAP ASE

• The Max_Used value reported by sp_monitorconfig for the configuration "number of locks" can report a values differently on running multiple times. At times it may report lesser value than the earlier reported for the max_used column.
• On running multiple times we may see the below symptom. The max_used value decreased by 41 locks between these two samples.
• First run date and time: Mar 30 2015 9:23AM.
  sp_monitorconfig 'locks'
  go
  Name                      Num_free    Num_active  Pct_act Max_Used    Reuse_cnt   Instance_Name
  ------------------------- ----------- ----------- ------- ----------- ----------- ------------------------------
  number of locks                  198991          1009   0.50          48286  0 NULL

• Now without restart the server, running second time may report like this.
  Second run date and time: Mar 30 2015 1:15PM.
  sp_monitorconfig 'locks'
  go
  Name                      Num_free    Num_active  Pct_act Max_Used    Reuse_cnt   Instance_Name
  ------------------------- ----------- ----------- ------- ----------- ----------- ------------------------------
  number of locks                  199053  1009   0.47          48245  0 NULL

• SAP Adaptive Server Enterprise (ASE)
• SAP Adaptive Server Enterprise Cluster Edition (ASE CE)

CR723588, CR#723588, 723588, CR#385854, 385854, CR385854 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , BC-SYB-ASE-CE , ASE Cluster Edition (Standalone) , Bug Filed