Cobol Json Parse / Json Generate not reversible when working with Numeric Edited Fields

Hello,

I would like to mention again 2 old Cases from me (TS010652468 and TS016864176), because the problem happened again with another Developer.

Can you please check the last Case (TS016864176), where some discussion took place and IBM decided to implement partially some changes, but we would like to check if it's possible to change it.
"The last comment was to open an IBM Idea:

You are correct in that the parsing of " 000" into a field with PIC -9(3) will not be changed with the proposed changes. In regards to the generate/parse not being inverse operations, I can only reiterate that this is not the current design of COBOL's JSON handling. I don't know if an IDEA (formerly RFE - Request For Enhancement) has been entered for this behavior, but that would be the official channel to request a change in behavior: https://ideas.ibm.com/?interaction=raised"

---

Problem Description:

It is about the results when generating and parsing fields with Numeric Edit Fields (for example PIC -9).

Using the phrase from the Developer to explain:
We have a field in a Copybook that is declared as PIC -9(3).

With this field format, JSON GENERATE and JSON PARSE do not work symmetrically / not reversible.

JSON GENERATE writes the base value 0 as the string " 000".
JSON PARSE, however, expects a numerical value in return. (0 instead of " 000" works.)

We understand that a numeric edit field is a kind of Alphanumeric, but when parsing it should at least recognize and convert it correctly.
In the last CASE was told that it "works as designed".
Fine, but in case we convert Numeric Edited Fields it requires some workarounds.
We have already identified 2 Workaround:
1) Using Cobol Function NUMVAL to convert the Numeric Edited Field before the Json Generate - so it will generate correctly numeric - but we always need to know the content of each field, and a special check in case the field is NULL. The olf fashioned DEEDIT.
2) Replace the PIC -9(3) by PIC S9(3) SIGN LEADING SEPARATE in Copybook. So we have the sign separated and can be converted correctly. Also fine, but it requires changing a lot of possible copybooks.

So, is it really working as designed ? Numeric Edited fields should be considered an exception and be checked every time ? Or is it an error on JSON Generate or JSON Parse ?

Kind Regards,
Eduardo Carrara
R+V Versicherung
eduardo.carrara@ruv.de