Re: %parms value when calling from SQL UDF.

Mail List wrote:
> 
> 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?

Yes, it applies to subprocedures too.  ILE RPG and ILE CL both pass the
mini-operational descriptor that gives the %parms info.  ILE C and ILE
COBOL do not do this by default, but you can get them to do it (for C,
it's #pragma, I forget which one; for COBOL, I think you say something
like 'BY DESCRIPTOR' on the call).

"unavailable" means the information wasn't passed on the call.  If this
happens, the RPG generated code sets the value to -1.  If I recall
correctly, it isn't always possible to detect that it wasn't passed - in
that case, it might just be garbage.