Re: SQL exception diagnostics

[Bruce Vining <bruce.vining@xxxxxxxxx>]

I find this approach a bit unpleasant in that it requires a change to the
procedure, but you could always use SQLs CALL to run a simple CL program
that issues STRDBG.  Normally I would just service the job but that isn't
too great in your situation either...  Hopefully someone on this list can
come up with a better solution.

On Fri, Jan 10, 2020 at 11:03 AM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

> I'll see what I can find about getting in debug mode.  Thank you
>
>
>
>
> -----Original Message-----
> From: Rob Berendt [mailto:rob@xxxxxxxxx]
> Sent: Friday, January 10, 2020 8:27 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: SQL exception diagnostics
>
> I seem to remember that the trick of using STRDBG to get further
> information from STRSQL was rather deprecated for getting it from
> performance information.  Not that I have further details but it may be a
> train of thought to pursue.
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
> to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com