Re: Find *ERR -- 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: Re: [WDSCI-L] Find *ERR
From: J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx
Date: Mon, 20 Sep 2004 13:31:54 +0200
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>

Matt,

According to the help text Alt-N should find the next error. Alas, this 
does not work; Alt-N just opens the 'Navigate' menu. Probably a leftover 
from Code/400, where it does work.

Joep Beckeringh


>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

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.