Robert,

The method most analogous to the SEU F15 browse is Ctrl-2 to split view, click on subroutine name in Outline View to position the new view to the subroutine, do whatever, Ctrl-0 to close the second view. Note that new views opened this way can all allow editing, and you can have up to 5 views open on a single member, not just 2 as in SEU.

Alternately, I'll just go to the subroutine by clicking on it in the Outline View, do whatever, and then return to the Exsr by clicking on the line number where the subroutine is used.

A third way is to set a quick mark and return to it.

A fourth way is to set a named mark and return to it.

A fifth way that I used a lot in CODE but don't use much in WDSCi (because the Outline View is easier) is to filter the source by the subroutine name (either Ctrl-F, enter name, click All, or right click, Selected, Filter selected, which can also be set up as a key combo if you like), put the cursor on the Exsr or Begsr as you choose, and then Ctrl-W.

There are probably others, but these are the ones I use.

Dave Shaw
Mohawk Industries

----- Original Message -----
From: "Robert Rogerson" <robertrogerson@xxxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Thursday, November 29, 2007 10:44 AM
Subject: [WDSCI-L] WDSCi vs SEU F15=Browse options


When using SEU to read code many times I would have the screen split with
two version of the source open. When I came to an Exsr I would switch to my
second view to see the code for the subroutine. When finished I would
switch back to the original member which was still positioned at the Exsr
statement.



I'm wondering how others do this in WDSCi

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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 here. If you have questions about this, please contact [javascript protected email address].