Re: SQL exception diagnostics

Hi Justin

Getting debug going on the job should always put the optimizer messages into the job log. That SHOULD include using an SEP, then maybe not having any breakpoints set. I forget if when in the graphical debugger, that it will still stop at the start. Worth a try, eh?

Vern

On 1/10/2020 7:56 AM, Justin Taylor wrote:

Well that's going to be tricky since I'm working with a stored procedure called via ODBC. Is there another way?

Thanks



-----Original Message-----
From: Birgitta Hauser [mailto:Hauser@xxxxxxxxxxxxxxx]
Sent: Thursday, January 09, 2020 11:11 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: SQL exception diagnostics

No. How I turn that on? Is it a SET OPTION?

Just execute STRDBG (without parameters) before calling your program. SQL messages are then logged within the joblog

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok) "What is worse than training your staff and losing them? Not training them and keeping them!"
"Train people well enough so they can leave, treat them well enough so they don't want to." (Richard Branson)


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin Taylor
Sent: Donnerstag, 9. Januar 2020 21:16
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: SQL exception diagnostics

No. How I turn that on? Is it a SET OPTION?