I have a very large customer which does exactly the opposite
of this.  They upgrade the development systems LAST just so they
can continue their development/roll-out process even with
multiple operating systems in play.  Now granted they can't
avail themselves of the new features for a while, but at least
they have that continuity which would otherwise be missing.
This is especially important for those sites with a large
number of systems where it can literally take months to
complete the installation of a new OS across all of the systems.

Regards,
Michael L Gueterman
Easy Does It Technologies
http://www.editcorp.com
voice: 888.858.EDIT or 573.368.5478
fax:   573.368.5479
--

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Cecile Chi
> Sent: Wednesday, October 04, 2000 7:06 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Compile on 6.5; run on 6.0 (or 5.5)
>
>
> This is not a new problem - I remember having to keep an older Fortran
> compiler on a test/development machine until the production machines
> had been updated to the later MPE release.
>
> Sites which have more than one HP3000 usually upgrade MPE on the test
> machine first, and then have this period of discontinuity.
> Will keeping the
> older Cobol compiler on the 6.5 machine solve the problem, or will the
> program code still contain anything that will cause a problem
> on 5.5 or 6.0?
>
> Cecile Chi
>