Implementation of DATATYPE DECFLOAT in the creation of an index in DB2 for z/OS

The customer uses DATATYPE DECFLOAT to represent floating point numbers to a base of 10 instead of the base 2 to avoid rounding errors. On DB2 distributed the DATATYPE DECFLOAT is indexable and everything works as required. Requirement is that DATATYPE DECFLOAT should be indexable for DB2 for z/OS.
Detailed description why we need DECFLOAT:
Because not all platforms, compilers, etc store/process floating point numbers the same call floating point in general is a very problematic issue, especially if expecting exact representations. For instance, DB2 for z/OS uses hexadecimal floating-point (HFP) numbers, whereas the customer uses IEEE754 floating-point numbers. Therefore when a client transmits data over the network we normalize in IEEE, but then on the zOS side we have to convert the IEEE to HFP - which most of the time is probably accurate, however it can result in very minor changes sometimes, but these changes can make exact number comparison very challenging. (e.g. 12345.000000 might get stored like 12344.999999) - when we output it we only output 2 digits to the right of the decimal so it rounds in both cases to 12345.00 - however if you did a DB2 sql with an equal sign, we can get 2 different answers depending on how we issue the query. If we use literal, like WHERE balance = '12345.00' - this would work, but if we used parameters markers such that the sql was WHERE balance = ?, then it's possible this wouldn't work. We have seen this with customers before.