× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Stephen,

You can't use countprefix to count the outermost element of a JSON document.  Instead, you'll need to use position 372 of the program status data structure to determine how many elements there are.

dcl-ds pgmStat psds;
  num_jsonDoc int(20) pos(372);
end-ds;

Good luck


On 6/14/2021 11:28 AM, Stephen Piland wrote:
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_" }');

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.