Re: SQL exception diagnostics

[Bruce Vining <bruce.vining@xxxxxxxxx>]

Is debug active for the job?

On Thu, Jan 9, 2020 at 1:09 PM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

> That just retrieves the job log.  I've already checked and the job log is
> of no help.
>
> Thanks
>
>
>
> -----Original Message-----
> From: Rob Berendt [mailto:rob@xxxxxxxxx]
> Sent: Thursday, January 09, 2020 11:43 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: SQL exception diagnostics
>
> If you use this API to retrieve the information from the current job do
> you see anything?
>
> https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/rzajq/rzajqudfjobloginfo.htm
>
> 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
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Justin Taylor
> Sent: Thursday, January 9, 2020 10:51 AM
> To: MIDRANGE-L (midrange-l@xxxxxxxxxxxxxxxxxx) <
> midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: SQL exception diagnostics
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> For a SQL statement, I can get the SQLSTATE and then use GET DIAGNOSTICS
> EXCEPTION to get the message text.  Is there any extended details that I
> can retrieve?
>
> This comes up occasionally.  The current instance is SQLSTATE 22018
> "Character in CAST argument not valid".  The obvious question is "CAST
> exception on what?".  Currently I do it like the dark ages of checking
> Christmas lights, check every bulb until you find the bad one.  I'm hoping
> there's a better way I just haven't learned yet.
>
>
> TIA
> --
> 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
>
> --
> 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