RE: Green screen - it's time is over/CODE/400

I've been using Code 400 in WDT 4.5 (sp2) for a couple of months now and it
mostly works.  If I took the trouble to learn more than the basics it would
be a lot faster than SEU.  As it is, having spent about ten minutes studying
it, I can do a lot of things faster.  Being able to tab from one position to
the next when editing RPG source without going into prompt mode makes me
very happy.  Designer makes me want to use externally defined print files.
<g>

I like it.  Verify doesn't seem any slower than a regular compile, but I'm
always connected to the 400 when I use it.

> -----Original Message-----
> From: Reeve Fritchman [mailto:reeve@ltl400.com]
> Sent: Tuesday, November 13, 2001 10:11 PM
> To: midrange-l@midrange.com
> Subject: RE: Green screen - it's time is over/CODE/400
>
>
> Well, it depends upon what your very special error is!  I had
> problems too
> (/COPY statements) but Violaine isolated it to a problem with the real
> compiler code and some of the "H" options.  Of course, a
> first-time verify
> is slower than a 170 with a cranked-down CFINT and the cache
> function is
> crude (it's not smart enough to know what source member/files
> have changed).
>
> I don't have time for troubleshooting either; hell, I don't
> have time for
> anything productive now that I'm reading your posts!  I was
> fired by the
> Farr-Coulthard show at the Rochester March pre-announcement
> meeting; came
> back; tried to get the damn thing to work; and ended up
> writing a letter to
> the iSeries High Commander questioning the Group's commitment
> to AD tools.
> But CODE/400 is one of those times when effort and
> persistence is worth it
> and I think the Toronto group is doing the best they can,
> given the lukewarm
> support of the iSeries management group.  Of course, CODE/400
> means nothing
> to the rest of IBM because it's not Linux...
>