Re:
> I can do a listf @.@,2 in MPE and it takes less than a second for 400
> lines to appear.  The same command in MPEX takes 8 seconds.

I didn't see a followup post from you saying that you solved
the problem.  So...

When encountering something like this, one has to ask
"if its slow, what is the process doing?".  There's usually
a simple answer to *that* question: Debug's "TR" command.

The next time you see a slow MPEX, determine the PIN
(<break>, :showproc   will show you the PIN), and with Debug,
get a stack trace.

From break:

   :debug
   pin #123        (where 123 is the PIN you found,
                    the "#" tells Debug "this is decimal")
   tr,i,d

or, from another session:

   run main.pub.vesoft; debug

   pin #123; tr, i, d
       (both commands are on the same line, this is important!)
   pin #123; tr, i, d
   pin #123; tr, i, d
   pin #123; tr, i, d
        (I.e., do a few traces, because if PIN 123 is executing,
         Debug has a hard time getting a valid stack trace 
         from *your* process of *another* process.)

       (and, later...)
   c
   exit

Note: the above may require PM capability.  If necessary, 
signon as MANAGER.SYS to do it.

Post the stack traces.

Stan
-- 
Stan Sieler
[log in to unmask]
www.allegro.com/sieler/wanted/index.html 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *