Re: null for YAJLINTO

Thank you, Scott, and also Jon.

I tried the second option before receiving your mail. I was afraid to
assign a number to an alpha field, now from your message I know it Ok.

It is working now, but it assigns 0 to the other alpha fields. In this case
it does not bother me. Otherwise I will change to your option 1.

You solved my problem.


On Tue, Aug 4, 2020 at 2:07 PM Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
wrote:

Hi Raul,

Its important to understand that the 'DATA-INTO' opcode does not tell
the parser program the data type of your field. So you might think "My
risk_index field is a number, YAJLINTO should be smart enough to know
that it can't assign a character value to it" but, indeed, that's
exactly what is happening here...

YAJLINTO defaults to assigning a character value of '*NULL' to any field
that is null in the JSON. Since risk_index is numeric, it can't accept
a character value of '*NULL'

Your options are:

1) Change risk_index in your DS to be a character field. (This is what
I would do.) That way, you can check to see if it contains *NULL, and
if so, you'll know that null was the value provided in the document.
When you need to use it in a numeric calculation, simply do
numeric_field = %int(risk_index), very easy.

2) Change the value that YAJLINTO uses for nulls to be a valid number.
That is done with a %PARSER option like this: %parser('YAJLINTO': '{
"value_null": "0" }'); -- in this example, I'm assigning 0 to fields
that are null. I don't think this is the best option, however, because
this applies to all fields with a null value. So, card_source,
card_country and authorization_number will all get assigned a 0, even
though they aren't all numeric. And, this can make it hard to
understand the data you're getting, and hard to detect if the field was
null vs. had a numeric value.

Therefore, I would prefer option 1.

-SK


On 8/4/2020 12:17 PM, Raul Alberto Jager Weiler wrote:

I received a json document with some fields null, and that causes RNX

0356

"jsondoc.operation.security_information.risk_index."
This is the document I get:
below is the DS: What can I do?
__________________________________________
{
"operation": {
"token": "3910336e4940927c95d8fb8a4be48a9f",
"shop_process_id": 13813001,
"response": "S",
"response_details": "Procesado Satisfactoriamente",
"amount": "48000.00",
"currency": "PYG",
"authorization_number": null,
"ticket_number": "2466114087",
"response_code": "58",
"response_description": "Transaccion denegada",
"extended_response_description": "EL ESTADO SWITCH DEL
CLIENTE/SUCURSAL ESTA INACTIVO \"I\" - GET024",
"security_information": {
"customer_ip": "201.217.58.22",
"card_source": null,
"card_country": null,
"version": "0.3",
"risk_index": null
}
}
}
______________________________________________
dcl-ds jsonDoc qualified;
dcl-ds operation;
token char(32) ;
shop_process_id packed(15) ;
response char(1) ;
response_details varchar(60) ;
amount packed(15: 2) ;
currency char(3) ;
authorization_number char(6) ;
ticket_number packed(15) ;
response_code char(2) ;
response_description varchar(40) ;
extended_response_description varchar(150) ;
dcl-ds security_information;
customer_ip varchar(40) ;
card_source char(1) ;
card_country varchar(60) ;
version varchar(5) ;
risk_index packed(1) ;
end-ds;
end-ds operation;
end-ds;

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com