HP3000-L Archives

December 2008, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Duane Percox <[log in to unmask]>
Reply To:
Duane Percox <[log in to unmask]>
Date:
Sat, 27 Dec 2008 09:03:52 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (44 lines)
Paul writes:

>Yep- so I am arguing with HP over the license on Telzy. They say it is  
>licensed for COBOL and MPE/IX 6.5, but it only has MPE/IX 6.0 on it.   
>They were not so sure about "downgrade" rights.

The problem you are finding also can happen if you ship an nmobj file that gets
added (with linkedit) into an xl from a newer system to an older system that has
a version of the millicode library that is missing those routines. This is because
linkedit gets the code at addxl time to add to the xl from the milli.lib.sys file.

This created a bunch of hassles for those of s/w vendors supporting customers on
different versions of mpe after they had migrated to the newest 7.x boxes.

I won't tell you what we did to resolve this, but I will list some data points we
discovered that you might find helpful. Keep in mind we are not HP system gurus
and this information was derived from empirical testing a number of years ago.

* The millicode library is MILLI.LIB.SYS

* You can file equate MILLI.LIB.SYS=<another version of milli.lib.sys> prior to any linkedit
   activity and you will get routines from the 'other' version of milli.lib.sys.

* There is nothing special about MILLI.LIB.SYS and newer versions seem to be compatible with
  reasonably older o/s versions since it is a code repository.

And finally, let me say that while people (as I) have always like mpe, there has always been
issues with supporting multiple o/s versions as an ISV because HP's stance was always forward
compatibility and during my tenure as an ISV I have had a number of occasions where compilers
and other tools were upgraded in a way that made our code developed on the current o/s version
not be installable/runnable on earlier versions without some workaround.

At least in this case it was documented. Back in the 'good ole' days there were occasions where
the changes and potential impacts were not documented and the issues had to be discovered by 
customers.

Good luck on your problem resolution, but I bet from the data presented you might have an idea
of the easier route to take :-)

duane

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

ATOM RSS1 RSS2