× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



If your using C#.NET and RPG wouldn't it be a good idea to parse inbound XML
data using C#.NET and pop it into a DB2/400 table and then use RPG for easy
onward processing (and vice versa in reverse for outbound XML data)?

Best of both worlds maybe...

Maurice O'Prey
XMLi5


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Mike
Sent: 01 December 2009 5:58 PM
To: .net use with the System i
Subject: [SystemiDotNet] Passing XML back and forth with RPG and .NET

I am at a loss here of a best-practice to pass XML back and forth with RPG
and C#.NET. Originally, I was going to use a temp physical file in QTEMP,
but it seems to be that there should be a better way. The temp file has one
line of the document in one record of the file. To me this seems to add a
lot of extra work that really shouldn't be needed. I am looking for a
two-way communication.

One thought is to pass a 32000 char parameter back and forth, but is that
really a good idea? What happens if the document happens to be bigger than
that? I don't think I would hit that limit so maybe I would be fine?

What about creating a temp IFS file? That seems like more work than is
needed as well.

What are your thoughts?

Obviously, both the RPG and C# programs will be reading and processing the
XML document.

I may x-post this on RPG-L as well.

--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.