Re: %parms value when calling from SQL UDF.

My only direct experience of this is in relation to SQL UDFs. There, the
value of %parms appears to be -1 when a procedure is called by SQL. That;s
as far as I can comment, I'm afraid.

"Mail List" <maillist@xxxxxxxxxxxxxxx> wrote in
message news:019d01c33b56$e0b28d10$6601a8c0@xxxxx
> Hi Pete,
>
> So does the same caveat apply to %parms when used in a subprocedure?  That
> is, if the subprocedure is called by some program that does not pass a
> minimal operational descriptor, will %parms be unavailable?  No mention is
> made of which languages would do that btw.  And what does "unavailable"
> mean?  Is it zero?  Or will I get an error if I try to use it?  Do I have
to
> start putting in error trapping for this situation in my subprocedures?
>
> Peter Dow
> Dow Software Services, Inc.
> 909 793-9050 voice
> 909 793-4480 fax
> 909 522-3214 cell
>
> From: "Pete Clifford (ariadne software)"
> > The *parms field in the PSDS denotes the number of parameters passed to
> the
> > main procedure/entry point. %parms here will give the same answer.
%parms
> in
> > a subprocedure is the number of parameters passed to that subprocedure.
>
>
> _______________________________________________
> 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.
>
>