Re: Parsing JSON data with DATA-INTO

Subject: Re: Parsing JSON data with DATA-INTO - V7R2
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Fri, 27 Apr 2018 15:32:36 -0400
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 2018-04-27 12:56 PM, Jim L. Bostwick wrote:

Thanks for the reply Barbara. The data-into statement I was using was passing a variable with a concatenated empty field rather than quoted text. ...

Hi Jim, it turns out that the compiler is optimizing away the concatenation of the empty literal '', so
parseOpt + ''
is being treated as though it were just
parseOpt

The compiler is passing the address of parseOpt, and the parameter passed to the parser has the userParmIsNullTermString subfield set to *off.

If you append a blank instead of an empty literal, it will work.

%parser(parseOpt + ' ')

As an Amazon Associate we earn from qualifying purchases.

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.

Re: Parsing JSON data with DATA-INTO - V7R2