Newsgroups: comp.sys.hp
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!hellgate.utah.edu!peruvian.utah.edu!knechod
From: knechod%peruvian.utah.edu@cs.utah.edu (Kevin Nechodom)
Subject: Re: HP3000/9xx Software Wanted
Date: 11 Jun 91 08:46:30 MDT
Message-ID: <1991Jun11.084630.27061@hellgate.utah.edu>
Organization: University of Utah CS Dept
References: <1991Jun4.213903.24875@ncsu.edu> <48580033@hpcupt3.cup.hp.com>

In article <48580033@hpcupt3.cup.hp.com> dhandly@hpcupt3.cup.hp.com (Dennis Handly) writes:
>>/ cocoiii@hobbes.catt.ncsu.edu /  2:39 pm  Jun  4, 1991 /
>>Right now, we have working versions of both on our HP3000, but if a
>>major operating system change occurs, it could stop.
>>only have it for the future if something changes in the OS. 
>
>Usually on MPE, OS changes never cause (correct) working programs to fail.
>
>Some customers have programs > 10 years old that continue to work.
>
>(but anything can happen, and does.  :-)

I have two experiences that may be considered relevant.
1)  I have a Fortran program running for which I have lost the source code.
    I have gone through at least three (soon to be four) OS updates with no
    problems whatsoever.  However, it is small.

2)  I use to run SPSS 9.X on my MPE V Series 48.  After some updates, I would
    get stack overflows.  SPSS supplied routines for sizing their own stack
    requirements, so I was easily able to recover.

From this, I conclude:  a) HP does an excellent job of maintaining
compatibility, unless b) you are running at the limits of your stack space.

With that said, I also note that you are talking about an MPE-XL machine, which
should not even have that problem.

Hope it helps.

Kevin Nechodom
University of Utah CSSRD
nechodom@cc.utah.edu
I am disclaimed.