RE: Performance - perception is King

>Is it possible that you (Toronto) are 
>populating the entire list before returning 
>control to the user? Is it possible to return 
>the first visible entity ASAP (first 
>screenful, e.g.)? 

This is one of those places the 5250 world differs from the GUI world.  If
one doesn't load the entire list, how big should I make the scroll bar
'cursor'?  Normally, GUI apps have a big fat cursor when there are only a
few items scrollable, and a teeny-tiny one when there are many items in the
list.  Sure seems like a pain, but the time it takes to load that list is
one reason the GUI people use progress bars for 'long running' processes.  

I think it's just something I need to get used to.  In Code, I create a
project which has fairly tight filters.  Also, I have a strong tendency to
check members out into a very small 'development' library, where the time to
load every member is negligible.  So now I have several small libraries,
each containing work in progress.  I have no idea if the concept is
reasonable to keep editor/workbench performance high, or just another case
of me having low standards and being willing to work with... less than
optimum conditions.
  --buck (at Code V5R1M0 for now...)