Re: Debugging A Stored Procedure -- MIDRANGE-L

Subject: Re: Debugging A Stored Procedure
From: dlclark@xxxxxxxxxxxxxxxx
Date: Mon, 16 Apr 2018 11:39:58 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 04/16/2018
06:29:12 AM:

I am using Rational Developer for i version: 9.6.0.1 and Data Studio

4.1.3.

When using the "IBM SQL and Routine Development" perspective it allows

to debug a store procedure once and then throws an error.

Sorry I can't really help you with that. I do all my SQL Stored
Procedure debugging through the Run SQL Scripts option. However, I do all
my regular debugging through RDi and find that I often have to restart RDi
in order to get debug to work again after recompiling my program. But
this also happens only if I had removed the SEP and try to re-add it. So,
perhaps this is what is happening under the covers in the perspective you
mentioned.

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

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.