|
Hi Matt, There are several ways to do this: 1) You can press the next and previous problem buttons on the toolbar. This will move your cursor to the next/previous error. 2) You can use Ctrl-Shift-H for next error and Ctrl-Shift-Y for previous error. This will move your cursor to the next/previous error. 3) Depending on the release you are using, you could use the Filter->Errors menu from the popup in the Lpex Editor. This will filter out all your source and only show the errors. Hope this helps! Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab "Tyler, Matt" <mattt@wincofoods .com> To Sent by: "'Websphere Development Studio wdsci-l-bounces@m Client for iSeries'" idrange.com <wdsci-l@xxxxxxxxxxxx> cc 09/17/2004 04:16 Subject PM [WDSCI-L] Find *ERR Please respond to Websphere Development Studio Client for iSeries In SEU I can create a statement that is in error by the syntax checker. I can then search for *ERR. Is there an equivalent function in LPEX. Thank you, Matt Tyler WinCo Foods, Inc mattt@xxxxxxxxxxxxxx _______________________________________________ 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.
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.