-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JSON Response '#' in field name with '{' #115
Comments
Strange;
What is your job CCSID?
try to issue a CHGJOB ccsid(500) or set the ccsid for the job
Perhaps try to pull the latest new noxDb that sets the delimiters when the
service program JSONXML gets loaded .
…On Wed, Mar 1, 2023 at 8:40 PM bmcpherson-srlife ***@***.***> wrote:
Hello! I have been playing with ILEastic and NoxDB by trying to rebuild an
API we currently use, but within ILEastic. Something which I noticed in
rebuilding a GET request is that the one of the field names, which is
'liad#', is having the hash symbol replaced with a '{', resulting in
'liad{'.
If it helps, I'm using the following options in the json_sqlResultSet call:
JSON_ALLROWS
JSON_META
JSON_COLUMN_TEXT
JSON_CAMEL_CASE
JSON_GRACEFUL_ERRROR
Thanks!
—
Reply to this email directly, view it on GitHub
<#115>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVIPHTTBUGK2WUH7U6ENHDWZ6QZZANCNFSM6AAAAAAVMPE4JU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hi, First, I apologize for such a delay. Other issues took priority, but I had not forgotten about this project. I have since installed the latest (as of 2023-09-08) versions of both ILEastic and NoxDB and the issue is still occurring. The jobs are normally set to CCSID 37. Even submitting the job to CCSID 500 did not change the result of having the field name '#' character becoming '{'. Thanks! |
Ok, let me just try that here..
ons. 13. sep. 2023 kl. 21.29 skrev bmcpherson-srlife <
***@***.***>:
… Hi,
First, I apologize for such a delay. Other issues took priority, but I had
not forgotten about this project. I have since installed the latest (as of
2023-09-08) versions of both ILEastic and NoxDB and the issue is still
occurring. The jobs are normally set to CCSID 37. Even submitting the job
to CCSID 500 did not change the result of having the field name '#'
character becoming '{'.
Thanks!
—
Reply to this email directly, view it on GitHub
<#115 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVIPHRI6CF3XIM45O3MAVLX2H3SFANCNFSM6AAAAAAVMPE4JU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello! I have been playing with ILEastic and NoxDB by trying to rebuild an API we currently use, but within ILEastic. Something which I noticed in rebuilding a GET request is that the one of the field names, which is 'liad#', is having the hash symbol replaced with a '{', resulting in 'liad{'.
If it helps, I'm using the following options in the json_sqlResultSet call:
JSON_ALLROWS
JSON_META
JSON_COLUMN_TEXT
JSON_CAMEL_CASE
JSON_GRACEFUL_ERRROR
Thanks!
The text was updated successfully, but these errors were encountered: