Re: Limits of SQL SET variable

[Charles Wilt <charles.wilt@xxxxxxxxx>]

I gave you that an hour ago :)

Charles

On Wed, Sep 10, 2014 at 11:32 AM, Gary Thompson <gthompson@xxxxxxxxxxx>
wrote:

> For any whom have an interest, my co-worker Rod Hoskins found the correct
> syntax to use the result from an SQL Function:
>
> This example (using SQL naming) works on our V7R1 system:
>
> SELECT  outloc,  petable.cymdend AS batdat,  ctonum,
>                 CAST('4200' AS CHAR(4)) AS traidf,
>                 --   SET docnum = fsp975dnf(:outloc, :ctonum, :cymdend)
>                 FSP975DNF(fsp971p.outloc, fsp971p.ctonum,
> petable.cymdend) as Docnum
> FROM    lib1.fsp971p AS fsp971p
>   JOIN     lib2.petable AS petable
>     ON     fsp971p.centyr = petable.centyr
>    AND    fsp971p.period = petable.period
> GROUP BY petable.cymdend,outloc,ctonum,'4200'
> ORDER BY 1,2,3
> ;
> The commented line was my crude attempt to 'call' SQL function FSP975DNF
> The following line is apparently the correct way to 'call' an SQL function
> Thanks again to all you helpful Midrange mavens
> Thanks again Mr. Hoskins
>
> --
> 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.