Re: What features should I demonstrate as being smart in WSDCi?

I'm not a COBOL programmer, but one thing I find *very* useful is
Service Entry Point (SEP) debugging. It really helps with trying to
debug batch programs. I use it a lot for debugging web applications
that call RPG programs.
--
James R. Perkins



On Wed, Mar 17, 2010 at 13:46, Thorbjoern Ravn Andersen <ravn@xxxxxxxxxx> wrote:

Several years back WSDCi was evaluated in our organization by somebody
unfamiliar with Eclipse and rejected as he could not see any advantages
in using it with OPM Cobol (yes, not ILE) so we happily work with the
traditional green screens.

I may now have a chance for undoing that, and I was wondering if there
was more things that might be interesting to a CObol programmer than

* Many lines on the screen (as witnessed by the recent thread)

* Being able to do a lot of syntax checking while typing (and pressing
Ctrl-S)

* Having compiler errors in a window and inlined in the editor (I can
compile a simple Cobol program to do this)

* Having an outline of your source

* Navigate libraries, and files and members, and using RSE Extensions
seeing spool files etc.

I have considered demo'ing RDP instead but I believe the price tag would
be strongly prohibitive.

Any suggestions?

--
 Thorbjørn Ravn Andersen  "...plus... Tubular Bells!"

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & 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.