New JSON Publishing functions - bug with JSON numeric types?

Hi All,

I was hoping to use the new JSON Publishing functions in a current project.
I've installed the relevant TR and have access to the new functions, which
mostly seem very good.

However, it seems to me that there is a bug in the json_object() function.

To illustrate - here is some sql which tries to build a json object in two
ways -
in t1 it is using the new json_object() function
and in t2 I've just built it manually.

What I expect is: {"amount":0.5}
but what json_object is giving me is: {"amount":.5}
i.e it is not inserting the 0 before the decimal point.

I also use the IS JSON predicate to indicate that the json object built by
json_object() is not valid JSON:

with t1 as (
select 'auto' as coltype, json_object( 'amount' value 0.5 ) as data
from sysibm/sysdummy1) ,
t2 as (
select 'manual' as coltype, '{"amount":0.5}' as data
from sysibm/sysdummy1)
select coltype, data,
case when data is json object then 'Y'
else 'N'
end as validjson
from t1
union all
select coltype, data,
case when data is json object then 'Y'
else 'N'
end as validjson
from t2;

This yields:
-- COLTYPE DATA VALIDJSON
-- auto {"amount":.5} N
-- manual {"amount":0.5} Y

Am I missing something or is this a bug?
Any advice on how to report this?
I would much prefer to use these functions to build my json objects but my
project has some pretty tight deadlines.

Thanks and best regards,
Craig