Re: Finding the length of a passed parameter

If you are in ILE and the variable is of a fixed length, then %len( %trim(
parm01 ) ) should give you the length of the passed parm. Is this what you
are looking for ?

Narayanan Pillai

----- Original Message -----
From: "York, Albert" <albert.york@xxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, September 18, 2003 11:17 AM
Subject: RE: Finding the length of a passed parameter


> Normally I would know the length.
>
> However, I am writing a program which will accept a variable number of
> parameters of different length. I can easily find out how many parameters
> were passed but I am looking for a way to find out how long each one is.
In
> my program I can allow for the maximum length and subscript as needed.
>
> For example:
>
> *ENTRY   PLIST
>    PARM              PARM01     256
>                PARM              PARM02     256
>
> Albert York
>
> -----Original Message-----
> From: Narayanan R Pillai [SMTP:strqst400@xxxxxxxxx]
> Sent: Wednesday, September 17, 2003 5:33 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Finding the length of a passed parameter
>
> On Wednesday 17 September 2003 20:16, Barbara Morris wrote:
> > Narayanan R Pillai wrote:
> > > On Wednesday 17 September 2003 18:17, York, Albert wrote:
> > > > Is there an API which will give me the actual length of a
> parameter
> > > > that is passed to my program?
> > >
> > > If you are using ILE, CEEDOD
> >
> > But CEEDOD only works with bound calls, not program calls.
>
> Oh absolutely, he said ginning sheepishly, that and if you use
> OpDesciptors(
> OPDESC) . However, if you are passing through a CALL, would  you not
> already
> know the length, even if you are passing pointers ?
>
> Narayanan
> >
> > _______________________________________________
> > 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,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
> _______________________________________________
> 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,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> _______________________________________________
> 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,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.