Re: [EXTERNAL] Source parsing, for outline, performance

I have mostly seen the extreme slowness in programs with very large copy books.  These copy books rarely change, so if copy books could be parsed/cached locally I think it might dramatically improve performance.  A copy book should only be reprocessed if it changes.  A copy book cache in our case would provide system-wide benefit because every program has the same copy book I am thinking of...









---- On Fri, 25 Jul 2025 12:05:40 -0700 Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote ---



Yes, I have... mine sometimes never finishes parsing. I experienced this in 9.6 as well.

I have also noticed that the feature that allows you to hover over a procedure to see the "comments" from the prototype source doesn't always work. I end up closing and restarting RDi.

Like others, I chalked this up to Java as well.

-----Original Message-----
From: WDSCI-L < mailto:wdsci-l-bounces@xxxxxxxxxxxxxxxxxx > On Behalf Of David Gibbs via WDSCI-L
Sent: Friday, July 25, 2025 11:12 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries < mailto:wdsci-l@xxxxxxxxxxxxxxxxxx >
Cc: David Gibbs < mailto:david@xxxxxxxxxxxx >
Subject: [EXTERNAL] [WDSCI-L] Source parsing, for outline, performance

Folks:

Does anyone know why RDi 9.8 takes such a long time to parse the
source to update the outline?

Frequently I've observed the 'live parsing' takes multiple minutes ...
most of the time the progress is shown as 0%.

Granted, the source I'm editing has a lot of copy members, but
(according to the log) the parser is using a cached copy of the copy
member.

Is anyone else seeing this behavior?

Thanks!

David