Do you need a DCL-S before the "num_jsonDoc" field to define it as a standalone field?
Eric Hill
Senior Software Developer
Integrated Corporate Solutions
ehill@xxxxxxxxxxxxx
256-760-8239
NOTICE:
This message may contain privileged or otherwise confidential information.
If you are not the intended recipient, please immediately advise the sender
by reply e-mail and delete the message and any attachments without using,
copying or disclosing the contents.
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Stephen Piland
Sent: Monday, June 14, 2021 11:29 AM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: YAJLGEN and Supposedly Simple JSON
CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
I'm probably missing something super simple because I've used YAJLGEN to aid in creating process of DATA-INTO on some super complicated.
Below is the code generated by YAJLGEN and it looks OK to the eye, but then the compiler obviously doesn't like num_jsonDoc 'outside' of the data structure.
Also below is a sample message used to generate the data structure. Any ideas how to tweak to get this working? Thanks!
==================================================
num_jsonDoc int(10) inz(0);
dcl-ds jsonDoc qualified dim(3);
ID varchar(9) inz('');
LASTUPDATETIME varchar(20) inz('');
end-ds;
=================================================
[
{
"id": "420319359",
"lastUpdateTime": "2021-05-27T17:37:14Z"
},
{
"id": "42I0187208",
"lastUpdateTime": "2021-04-22T18:41:58Z"
},
{
"id": "42I0187209",
"lastUpdateTime": "2021-04-22T18:41:59Z"
}
]
===================================================
data-into jsonDoc %DATA( ifsPathname
: 'doc=file case=convert countprefix=num_')
%PARSER( 'YAJLINTO'
: '{ "document_name": "jsonDoc", +
"number_prefix": "YAJL_" }');
--
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
As an Amazon Associate we earn from qualifying purchases.