Re: opdesc and arrays

["Rory Hewitt" <roryhewitt@xxxxxxxxx>]

Larry,

I think they are not.

You could always pass a single blank element as the last element of the
array (after all the real elements) - that's what I tend to do.
Alternatively, pass a data-structure as the second parameter which consists
of an index value (10I) and the array, e.g.:

D ArrayDS          DS
D   lp_policyCount                   10I 0
D   lp_policyNo                           9A   Dim(32767)

I also do this a lot in my programs as it keeps the array and its index
together at all times, so no need to define stand-alone variables. You can
also include a lookup/positioner in the DS as well as the index for %LOOKUP
operations...

Rory


On 1/7/07, Larry Ducie <larry_ducie@xxxxxxxxxxx> wrote:
> Hi chaps,
>
> Is this right? Are operational descriptors are not passed for arrays?
>
> I have a procedure interface with an array defined as follows:
>
> D pr_MyProc        PI                  opdesc
> D  lp_Cli                       10a   const
> D  lp_policyNo                   9a   dim(32767) options(*varsize)
> D  lp_polCount                   5u 0
>
> I was hoping to determine the length of the passed array without the need
> for the caller passing in an element count but when I check the length of
> the second argument (via a call to CEEDOD) I get: CEE0502 - Missing
> operational descriptor. I put a quick line in to check the first argument
> and it worked fine.
>
> I have recompiled the caller (which is also a ILE RPG program) and
> everything else seems right. Are arrays not supported for operational
> descriptors in ILE RPG?
>
> Cheers
>
> Larry Ducie
>
>
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.