RE: JSON un-named arrays

I can tell you that the YAJLGEN command didn't like it... It did not "see" past the "data" array

dcl-proc readTheJson;

dcl-ds jsonDoc qualified;
RECORDS packed(1) inz(0);
FIELDS varchar(29) inz('');
num_DATA int(10) inz(0);
DATA varchar(1) dim(1); // empty;
end-ds;



-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Brad Stone
Sent: Monday, July 17, 2023 12:01 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: JSON un-named arrays

Looks funky.. data is an array with another array of elements in it. I'll
be interested to see the answer to this one. It's probably more simple
than I can think of... I'm sure I could figure it out using straight YAJL
but DATA_INTO is something I'm using more these days too...

num_data int(10);
dcl-ds data dim(x);
num_nothing int(10);
dcl-ds nothing dim(y);
....

??

On Mon, Jul 17, 2023 at 10:31 AM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Typically, I use DATA-INTO and the YAJLINTO parser... But I'm not sure if
that's possible with the JSON below. The array "data" contains an un-named
array of values.

Any suggestions on how handle reading this?
Do I need to use the YAJL "tree-based" method?

{
"records": 4,
"fields": "trano,ref,duedate,name,amount",
"data": [
[
1,
"40061433",
20230719,
"Mudpie",
187.2
],
[
2,
"40061349",
20230719,
"kiddywampus",
156.21
],
[
3,
"40062677",
20230721,
"Chase",
70.8
],
[
4,
"40061703",
20230723,
"Stamford Toys",
110.7
]
]
}
[Logo]<https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
1 Corporate Dr
Grantsville, MD 21536
www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>
--
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.