RE: Debug SQL stored procedure?

I didn't have DEBUG mode set.

Can Run SQL Scripts debug another job? The stored procedure itself works fine. The IIS client is having issues, so I need to debug their QZDASOINIT job to determine what's going wrong.

Thanks



-----Original Message-----
From: Charles Wilt [mailto:charles.wilt@xxxxxxxxx]
Sent: Monday, July 08, 2019 12:14 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Debug SQL stored procedure?

make sure to include
ALLOW DEBUG MODE

or SET OPTION DBGVIEW=*SOURCE

"If DEBUG MODE is not specified, but a DBGVIEW option in the SET OPTION statement is specified, the procedure cannot be debugged by the Unified Debugger, but can be debugged by the system debug facilities. If neither DEBUG MODE nor a DBGVIEW option is specified, the debug mode used is from the CURRENT DEBUG MODE special register."

IIRC, RDi counts as the "Unified Debugger"...

I usually use the System debugger via Run SQL Scripts...

HTH,
Charles



On Mon, Jul 8, 2019 at 9:20 AM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I'm trying to debug a Db2 stored procedure (SP) with a Type of SQL.
I'd prefer RDi, but the only thing I could find was for 5250 (
https://www-01.ibm.com/support/docview.wss?uid=nas8N1017447). When I
tried to debug it, it says "(Source not available.)" and "Program &1
cannot be debugged.".

Any suggestions?


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