RE: Debugging Remote Stored Procedure Calls -- RPG400-L

Subject: RE: Debugging Remote Stored Procedure Calls
From: "Haas, Matt (CL Tech Sv)" <matt.haas@xxxxxxxxxxx>
Date: Thu, 5 Nov 2009 16:35:52 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

The only time I notice WSDC being slow is when there are massive amounts of variables. Clicking another tab on the area the variables show up in to hide them speeds things up considerable.

Matt

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Thursday, November 05, 2009 4:11 PM
To: RPG programming on the IBM i / System i
Subject: Re: Debugging Remote Stored Procedure Calls

Michael Scott - IS wrote:

Albeit, slow.

Slower than debugging it the old fashioned way? :)

IMO, SEP debug speeds up my development by a factor of 2 or 3. Especially since I'm often debugging 3 layers of code at the same time (client, server, and host).

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Debugging Remote Stored Procedure Calls , Bryce Martin

This mailing list archive is Copyright 1997-2025 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.