True enough, the program isn't "returning" anything, but the input parms that aren't designated CONST just might get loaded in the program making that payload accessible to the caller. IWS recognizes those as input/output, and if dimensioned, they get a COUNT value associated with them. In the "Select Export Procedures to Externalize as a Web Service - Step 4 of 9" stage, I can stuff a integer variable name in to restricts the array to that many occurrences. My program increments that variable as I load the array, and IWS requires that the integer variable be among the I/O parameters.
The part about functions needing to return the 4-byte integer to IWS is circumvented by specifying RTNPARM on the PR/PI.
Sorry to confuse. I'll get the "working version" of the prototypes to you tomorrow (assuming I can replicate the piece that worked earlier today before I "messed with it").
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon
Sent: Tuesday, December 30, 2014 5:37 PM
To: Midrange-L Midrange-l
Subject: Re: IWS needs web service to return only the array rows used
I'm confused Michael,
You say you "return a data structure" - but a) Programs can't "return"
anything and b) A service program function can return a DS - but would
still not work with IWS because it can't handle anything except a 4 byte
integer as the return value.
That would imply that you are always returning the values via I/O
parameters which makes your earlier comments about switching the way you
handled the results really confusing.
Can you clarify please _exactly_ what your prototypes look like in the
case where it works (the *PGM case?) and those where it doesn't.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives