Re: YAJL 1002 parse error: trailing garbage

Jon, Charles:

Well the thing is that I expected YAJLINTO to let me know who called it. I
will have to put up my own logs. I'm actually using another dev's work so
he's not using the (E) extender.

The issue here is that if that error is true then at the point where it's
happening, the rest of the call stack should be broken too but that is not
the case. So that's why I thought maybe it could parse successfully the
json but found more invalid data just after the last valid construct, and
is reporting it with no further harm. Then it becomes a warning. Maybe
Scott could give me his comments on the above.

Thanks folks!

message: 1

date: Tue, 22 Jun 2021 15:45:26 -0600
from: Javier Sanchez <javiersanchezbarquero@xxxxxxxxx>
subject: YAJL 1002 parse error: trailing garbage

Good day or evening:

I have been using DATA-INTO or DATA-GEN for some JSON messages. I am
getting in the submitted job's log the above message.

Is that 1002 really an error? Or is it a warning? I'm in a hurry on a
production box and have not much time to get what it is, as the flow of
calls to other programs show no other errors. And where is it generated:
on a DATA-INTO or a DATA-GEN or both?

Thanks in advance.