Provide ability for Omegamon to calculate space based on conversion factor of 1000 instead of 1024

Based on the OMEGAMON XE for Storage Users Guide (see below), space values displayed in the Tivoli Enterprise Portal (TEP) are based on a conversion factor of 1024. This is inconsistent with published IBM DASD volume capacity which uses a conversion factor of 1000. For example, IBM publishes the following capacity for a 3390 mod 9:

3390-9: Cylinders: 10017, Tracks: 150255, Bytes per volume: 8.51 GB, Bytes per track: 56664

To calculate Total Capacity in MB, IBM uses the following calculation:
Total Capacity KB = ((Tracks)*(Bytes per track))/1000
Total Capacity MB = (((Tracks)*(Bytes per track))/1000)/1000
Total Capacity GB = ((((Tracks)*(Bytes per track))/1000)/1000)/1000
8,514,049 KB= (150255*56664)/1000
8,514 MB= ((150255*56664)/1000)/1000
8.51 GB= (((150255*56664)/1000)/1000)/1000

OMEGAMON XE for Storage (Volume Space Report, Attribute: Total Capacity Megabytes) on the other hand uses a conversion factor of 1024, as follows:
Total Capacity KB = ((Tracks)*(Bytes per track))/1024
Total Capacity MB = (((Tracks)*(Bytes per track))/1024)/1024
Total Capacity GB = ((((Tracks)*(Bytes per track))/1024)/1024)/1024
8,314,320 KB= (150255*56664)/1024
8,120 MB= ((150255*56664)/1024)/1024
7.93 GB= (((150255*56664)/1024)/1024)/1024

Thus, OMEGAMON displays the value for Total Capacity Megabytes as 8120 but we are expecting 8,514. Due to this discrepancy, we are unable to use OMEGAMON to replace our current reporting tool.