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

× 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.

Subject: Re: Debugging Remote Stored Procedure Calls
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 05 Nov 2009 15:11:08 -0600
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>

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 , David FOXWELL
RE: Debugging Remote Stored Procedure Calls , Haas, Matt (CL Tech Sv)

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.