Re: JSON and the IFS

[Pete Helgren <pete@xxxxxxxxxx>]

If you are just checking the format, jsonlint.com is a great site to vet 
and ID any issues.  Copy and paste the data onto the site, it will tell 
you where the issues are.

On very complex JSON, it is a lifesaver and even on simple stuff, it has 
pointed me to really simple errors I have made....

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
LinkedIn - www.linkedin.com/in/petehelgren
Twitter - Sys_i_Geek  IBM_i_Geek

On 11/11/2016 12:18 PM, Booth Martin wrote:
> Thank you Kevin. Danny, Henrik, and Justin.
>
> Clearly, lesson 56 is to be learning about ccsid.
>
> Also, IE.   hmmmm    Good tip.  I tried IE 11 and discovered the data 
> on http://ventures.martinvt.com/ did not show up with IE either. 
> Apparently it only works in Firefox.
>
> Again, thank you all for the pointers.  Very much appreciated.
>
>
>
> On 11/11/2016 3:28 AM, Kevin Turner wrote:
> > It shouldn't have any problem as long as the data is correctly 
> > encoded. With JSON the typical mistake is with the braces ({}) 
> > especially when hardcoded in RPG source. If your job ccsid is 37 
> > (using the US example) and your source files is ccsid 37 then what 
> > you key in will look fine in the source and any file you spew out to 
> > the IFS, but that doesn't mean that it actually is correct when 
> > converted by Apache to (for example) UTF-8. We never hardcode those 
> > characters for that reason. It would be useful to see what Booth gets 
> > on the browser and if indeed it is the braces that are screwed.
> >
> > Sent from my iPad
> >
> > > >On 11 Nov 2016, at 09:00, Henrik Rützou<hr@xxxxxxxxxxxx>  wrote:
> > > >
> > > >I have had the same problem with IE loading external  XML via AJAX 
> > > into DOM
> > > >
> > > >On Fri, Nov 11, 2016 at 9:30 AM, Kevin 
> > > Turner<kevin.turner@xxxxxxxxxxxxxxx>
> > > >wrote:
> > > >
> > > > >>"First, its telling me the file is badly formed and points to row 
> > > > 1,"
> > > > >>
> > > > >>What is "it" in this sentence?  Your browser? If so what does the 
> > > > JSON
> > > > >>look like when it is downloaded? For example you can use the 
> > > > Google Chrome
> > > > >>developer tools - Network tab to look at it.
> > > > >>
> > > > >>Sounds to me like you have a ccsid issue with the file.
> > > > >>