× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I don't believe the system debugger can utilize SEPs.

Actually, SEPs should be possible with the system debugger:
http://ibmsystemsmag.com/ibmi/developer/general/service-entry-points-help-simplify-cgi-debugging/


Tim Clark
DB2 for IBM i


"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 07/08/2019
04:55:02 PM:

From: Charles Wilt <charles.wilt@xxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>,
Date: 07/08/2019 04:55 PM
Subject: [EXTERNAL] Re: Debug SQL stored procedure?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>

Run SQL Scripts uses the system debugger (which is a Java client app)
...

There is a place to enter "Existing Job to Debug"..

So yes, but the issue you might have would be if the client connects,
runs
the SP and then disconnects...

I don't believe the system debugger can utilize SEPs.

Charles


On Mon, Jul 8, 2019 at 2:35 PM Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:

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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.