Michael, you may want to try the Verify process that Peter mentioned. It's a bit cumbersome (verify, then compile), but it works. On 11/10/06, Michael Rosinger <mrosinger@xxxxxxxxx> wrote:
Michael, We are new to iSeries and I am just getting up to speed in WDSC. We will be migrating COBOL/DB2 programs from VSE to iSeries. The problem you described was one of the first I encountered and I consider it very serious. The IBM resource that has been assisting us suggested a circumvention, but that too has its set of problems. For the interim, the safest and least frustrating way that I've found is to open the spooled output from the compile that failed in a separate editor window and swap between it and the source window while fixing the errors. The good news is that this problem is getting more attention from development and I am expecting a fix very soon. -- Regards, Michael Rosinger Systems Programmer / DBA Computer Credit, Inc. 640 West Fourth Street Winston-Salem, NC 27101 336-761-1524 m rosinger at cciws dot com "Michael Ryan" <michaelrtr@xxxxxxxxx> wrote in message news:mailman.1066.1163164652.8229.wdsci-l@xxxxxxxxxxxxxxx > 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? -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.