The upgrade manual reads like one of the page flipping
adventure stories.  You only use about one-tenth the
material, the rest does not apply.

The results are the same too.  You either survive the
adventure, or end up dead.

(Note I'm not saying this is either good or bad make of
it what you will.)

Tracy M. Johnson
TRW Automotive Electronics
Sensors & Components

-----Original Message-----
From: Lars Appel [mailto:[log in to unmask]]

Larry wrote...
>In my opinion the thing that kills 3000s is not time but os upgrade
>complexity.  The manual for version 6.5 upgrade is about 1" thick.  Can I
>give this to a plant manager who currently just changes the tapes for each
>nightly backup and ask him to upgrade the os?  No way.  [...]

While I do agree that the MPE/iX install/update/patch procedures do
leave *lots* of room for improvement (the if's and goto's in the manual
should really be put into a program that either prints or displays a
customized step-by-step checklist or invoke the steps automagically)...

I also have to say that just last week a new colleague did perform
quite a number of tasks with that manual (install, patch, update) and
seemed to have close to zero problems. Notice that he did not yet have
a chance to visit the MPE/iX system manager class!

The thickness of the manual also results from the detail-level, I guess.

Lars.