Re: DATA-INTO where number of records not known

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Have you looked at using YAJLGEN to generate the DS & DATA-INTO call you
need?

You can do it yourself or course, but YAJLGEN sure makes for an easy first
pass.

Basically, in the data-into you include "count prefix" like so:
countprefix=num_

then in your DS, you include a field
dcl-ds jsonDoc;
  num_SOMEARRAY int(10);
  SOMEARRY char(10) dim(9999);
end-ds;

YAJLINTO will load the array and the value in num_SOMEARRAY will be how
many entries were loaded to the array.

Now if your # of entries exceeds the max array size for RPG, then I think
%handler() is your solution.

I've only seen it used once, and that was for XML...but it only processes
part of the doc at a time before passing the data to your handler.  A quick
serach didn't turn up a good exmaple of using it for JSON.

Teraspace and a based pointer might be another option if you're dealing
with really large documents...just a thought.

Charles




On Thu, Dec 10, 2020 at 3:01 PM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> (Sorry, not sure if this is should be the RPG list only or the Midrange
> list)
>
> We are using data-into with YAJLINTO to process a json file we retrieve
> from an external site using a web service.
>
> The web service does not provide any options as to controlling the number
> of records to be returned.
>
> The json returned does not have an element for the number of records
> provided.
>
> If I put a count at the highest level will this be set correctly if the
> number of records retrieved exceeds the array size ? And if yes how do I
> then process the records past that point ?
>
> I don't think the %handler option helps - well the way I read the doco it
> wont.
>
> How do I either check how many records have been returned or process a
> json string that exceeds the number of elements in my receiving array ?
>
> Thanks for all suggestions
>
> Don
>
>
> --
> This email has been scanned for computer viruses. Although MSD has taken
> reasonable precautions to ensure no viruses are present in this email, MSD
> cannot accept responsibility for any loss or damage arising from the use of
> this email or attachments..
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-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