That's exactly what we did.  VeSoft only told us to delete files with a
641 file code and couldn't help us beyond that when it was still slow.

Thanks Paul!

-----Original Message-----
From: Paul Taffel [mailto:[log in to unmask]] 
Sent: Monday, December 11, 2006 7:44 PM
To: Mimura, Paul ; [log in to unmask]
Subject: Re: MPEX slow, but not MPE

At 01:13 PM 2006-12-11, Paul Mimura wrote:

>Thanks Stan for the diligent follow-up.
>
>I should have posted that Paul Tafel's suggestion worked out.
>
>The suggestion was to restore the VeSoft account without the olddate 
>parm.
>
>Now I can't say that I really know why it worked, but it did work!


Well, as you've confirmed that it worked, now I can tell you why:

MPEX 'compiles' its internal command files (in its CMD22 and
EXP22 groups) into more efficient versions before executing them the
first time.

This compilation is re-triggered whenever MPEX determines that a command
file's creation date & time is later than the creation date and time of
the compiled version.  I imagine that you somehow originally restored
the files in the VESOFT account when your system clock was incorrectly
set to some future date.  After correcting your system clock, every time
that MPEX checks, it thinks that each and every command file needs to be
re-compiled, every time you issue any command.

This will slow things down very noticeably.

Hope this helps,

Paul Taffel

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