Jim,

while I am not an expert on XML, I have been using Transact programs
in CGI context for quite a while now. In it's simplest form, a shell
script in cgi-bin uses CALLCI to launch the Transact NMPRG, which in
turn generates the desired HTML output.

I'm not at the office, so here is the CGI plot quoted "by heart"...

 #!/bin/sh
 echo Content-Type: text/html
 echo
 callci myprog.grp.acct \"$QUERY_STRING\" < /dev/null > /tmp/mytemp$$
 cat /tmp/mytemp$$
 rm /tmp/mytemp$$

The Transact program has HTML tags added to the display statements;
it seems to me that generating XML should be possible in a similar
way...

 display
   "<h1>Just an example</h1>", line:
   "<p>Customer name:", line:
   (cust-name), join=1:
   "</p>, join=0;

Parsing XML would probably need some more work. If I had a need to
do so, I'd probably use a combination of Java Servlet and Transact
NMPRG, as the Java Servlet could probably use existing XML parser
code like Xerces from xml.apache.org and pass the extracted data of
interest to the Transact code then.

Similar to my "MPE Proglets" experiments, where a small Java Servlet
acts as "glue" between a regular Transact program and GUI or Web...

 Steal examples at http://www.editcorp.com/personal/lars_appel/  ;-)

Again, I am not claiming to be an XML expert. And I'm surely not
claiming that my examples at the above URL are the best way to go.
However, it was fun to create the Java program or applet acting as
a GUI front-end to a small Transact program accessing MUSIC DB.

Lars.

PS... Have you examined the various 3rd party solutions described
in the white papers on Jazz or at www.hp.com/go/3000 (regarding Web
or GUI evolution of HP 3000 apps) already?