Best Practice - Compiling SQLRPGLE w/Errors -- WDSCI-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: Best Practice - Compiling SQLRPGLE w/Errors
From: "Michael Ryan" <michaelrtr@xxxxxxxxx>
Date: Fri, 10 Nov 2006 08:17:18 -0500
List-archive: <http://archive.midrange.com/wdsci-l>
List-help: <mailto:wdsci-l-request@midrange.com?subject=help>
List-id: Websphere Development Studio Client for iSeries <wdsci-l.midrange.com>
List-post: <mailto:wdsci-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/wdsci-l>, <mailto:wdsci-l-request@midrange.com?subject=unsubscribe>

What's the best practice for fixing SQLRPGLE compile errors in WDSc? AFAIK,
the problem of double clicking the compile error and WDSc bringing up an
RPGLE member still exists. What's the best way to deal with this? Just deal
with it? :) Use a combination of green screen compiles and WDSc editing?

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Best Practice - Compiling SQLRPGLE w/Errors , Peter . Colpaert

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.