Re: how to handle option tag when using CGIDEV2 to create xml data

Couldn't you just change the template to be this:

/$myXMLSec_start
<Order>
/$myOptSec
<MyOptTag>/%myOptTag%/</MyOptTag>
/$myXMLSec_end
</Order>

with the RPG code as follows:

wrtSection('myXMLSec_start');
if John = Mary;
updHtmlVar('myOptTag' :'John is Mary');
wrtSection('myOptSec');
endif;
wrtSection('myXMLSec_end');

In other words, you're making your template more granular, by putting
optional tags in their own sections.

It keeps the HTML out of the RPG program, and it also makes it easier to add
more stuff (optional tags etc.) to the myOptSec section. On the downside, it
means you have to separately write the myXMLSec_start and myXMLSec_end
sections instead of a single myXMLSec section...

Rory

From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Lim Hock-Chai
Sent: Wednesday, February 18, 2009 12:57 PM
To: RPG programming on the IBM i / System i
Subject: how to handle option tag when using CGIDEV2 to create xml data

How does one normally handle optional xml tag when using CGIDEV2 to
create the xml data?

should I do something like below?

Template:
/$myXMLSec
<Order>
/%myOptTag%/
</Order>

RPG code:
updHtmlVar('myOptTag' :'<MyOptTag>blah blah blah</MyOptTag>');
wrtSection('myXMLSec');

Or is there a better way of handling this?

thanks