Re: Debugging an SQL UDF

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Include
set option
  dbgview = *SOURCE

When you create the proc.  Works like the list view in RPG, the source
is included in the compiled object.

Note: if you've hard coded a schema name on the create and you move
the object, the SQL source debugger gets confused and won't pull up
the source.

HTH,
Charles

On Wed, Apr 20, 2011 at 1:18 PM, James Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:
> I've been reading the Stored Procedure/Trigger/UDF Redbook, and in
> particular, the section on debugging UDFs.
>
> I tried it on a UDF that's giving unexpected results. Unfortunately that
> UDF doesn't have debugging data, and I don't know how to provide it.
>
> The UDF was created from a STRSQL session. While I've heard that one can
> also create it from a source member, I don't know the mechanics of doing so.
>
> The problem at hand is a go/no-go function for a censored VIEW, and it's
> returning a consistent "go" result, even though there are records for
> which it theoretically should be a "no-go".
>
> --
> JHHL
> --
> 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.