Re: XML-INTO - RNX0353 reason code 1

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

Hi Paul,

Again...  I'm just guessing as to why it's done this way, I wasn't "in 
the loop" when they designed this behavior...  but it seems to me that 
if you had XML data in a PF, it would explain why this behavior works 
this way.

For example, a PF with CHAR(40) records might look like this:

*...+....1....+....2....+....3....+....4
<myXmlFormat>
     <myCustomer>
          <myCustomerAddress>
              <street>854321 West
Lexington Avenue</street>

In this example, there'd be 7 blanks between 'West' and 'Lexington'... 
and an RPG programmer would probably be complaining about having to 
remove them.

I'm not saying they're right -- but, if you know RPGers like I do (and 
I'm betting you do) you just know they'll try to put XML into a flat 
file like this.



On 12/27/2010 4:29 PM, Paul Nicolay wrote:
> Hi Scott,
>
> Thanks once again... I clearly missed some options.
>
> Strange that a "trim" option also "trim's" embedded blanks (leading or
> trailing I would understand)... and even more strange that the default
> is on, which is against XML syntax !?
>
> Kind regards,
> Paul
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
> Sent: maandag 27 december 2010 19:43
> To: RPG programming on the IBM i / System i
> Subject: Re: XML-INTO - RNX0353 reason code 1
>
> hi Paul,
>
> There's an option for that, too.  Try specifying trim=none in your
> Options.
>
> I'm guessing that feature was put there because of RPGers insistence on
> putting XML data into physical files  (flat files) with fixed-length
> fields?  Once they've done that, there's no way the document can comply
> with XML standards -- but RPG programmers seem to like to put data into
> PFs.   The trim option (which is on by default) removes the extra spaces
>
> that the PF adds.
>
> Of course, for those who don't want it (you), just specify trim=none.