RE: Find *ERR

Violaine,
        Thanks for the tips, but only tip #3 works for what I am asking for.
The other two work for compile type errors and only if one accepts to insert
errors. There error I am looking for is a syntax checker error.  I use them
as a pseudo book marks, since I do not know of any __quick keystrokes__ for
setting, finding and clearing bookmarks.


Thank you,
Matt Tyler
WinCo Foods, Inc
mattt@xxxxxxxxxxxxxx

-----Original Message-----
From: Violaine Batthish [mailto:batthish@xxxxxxxxxx]
Sent: Monday, September 20, 2004 5:46 a
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Find *ERR




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.


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