The limitation you're talking about isn't actually from JT400. It's a server-side limitation from the Remote Command host server. If you look at the native cwb_* APIs for IBM i Access, you'll see they have the same foibles. So, the target of disappointment/jabs/anger/whatnot should be that server interface.
I like the concept of XMLSERVICE as a community-based replacement for the Remote Command server, but wish it would have reused the PCML/XPCML format for that part of its functionality ... although I guess that could be added. In an ideal world, adopting the standard format would allow IBM to update the baked-in PCML support in the RPG compiler.
________________________________________
From: web400-bounces@xxxxxxxxxxxx [web400-bounces@xxxxxxxxxxxx] on behalf of Jon Paris [jon.paris@xxxxxxxxxxxxxx]
Sent: Thursday, August 09, 2012 4:12 PM
To: web400@xxxxxxxxxxxx
Subject: Re: [WEB400] XMLSERVICE with .Net
On 2012-08-09, at 3:05 PM, web400-request@xxxxxxxxxxxx wrote:
I thought JT400 had trouble returning anything more than an INT from a subprocedure? Or am I mistaken...
XML Service certainly can.
Not only that Mike but it has significant limitations on the data types and types of DS it can handle. One of the reasons why Tony created XMLSERVICE.
V7 eased the return value problem (by accident as it turns out) through RPG's RTNPARM which automagically converts the return value to be the first parm.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/web400.
midrange.com
