Re: WDSc 5 is slow!

Mike,

Do these programs use a lot of files?  One thing the outline does is pull
in the files used by the program and all of their fields.  This seems to
take the longest, and unfortunately, I do not think it is making use of the
object cache that the program verifiers use.

It does seem to be using some kind of caching, as if you open the same
member again, the outline will build quickly, however it doesn't seem as
though different members that use the same files take advantage of that
caching.

The good thing about the outline is that it doesn't load by default, and
you do not need to load it to make a quick change.  Hopefully, they will
provide ways to speed it up and/or fine tune it.  For example, Code/400 had
a macro that listed all of the fields, indicators and subroutines used in
the program.  If they did something like this, and deferred loading the
file definitions until you asked for them specifically, that could help
while still giving us some of the features.

In the overall picture, setting aside some of these issues, I would think
it would be a little easier to work with these really large programs in
WDSC than it was in SEU.  I personally always found that to be the case
with Code/400 and was one of the main times when I would use it.

If you ever work on any "longer term" projects it might be worth looking at
the iSeries Projects feature.  This pulls the source you are working on
down to your PC so if you are going to be working on the same set of
programs for a few days you can work on it all locally and just upload it
when you want to build it.  This helps with the speed and quick access
issue (provided that you would be working on these items over a long enough
period of time to realize the benefit).

Mark