I think what you are referring to is GREB software which is still on the
market.
It has it's own repecussions.
For example: What if you replace a low end 918 with a 989/200, and then
you turn around it and give it the old HPSUSAN and the CPU string of the
918 so your old software will run on the higher end 989/200?
HP may not have a problem with it, however 3rd party software that uses
hardware tiers for pricing may ask you to pay the higher tier for the
base price and on their maintenance fee.
Tracy Johnson
Office 1-757-766-4318
[log in to unmask]
> -----Original Message-----
> From: HP-3000 Systems Discussion
> [mailto:[log in to unmask]] On Behalf Of Michael
> Sent: Friday, September 24, 2010 3:15 PM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Was HP3000 Services (longish), now HPSUSAN
>
> No, I remember when some BAD 3rd party companies got there hands on
> ssconfig back in the 90's. They were actually using ssconfig
> to convert
> HP9000 machines into HP3000's, and altering the user lic to
> unlimited.
> As I recall they made lots of money doing that, and later
> most of them
> did some time in jail, maybe still in jail, I donno!
>
> What I am referring to is not HP software, and it only changes the
> HPSUSAN and CPU string. Not to make lots of money and go to jail, but
> rather to replace a system board without application problems.
>
> I would NOT want to do anything illegal, and so I didn't pay much
> attention to it when I heard about a few years ago. So, would
> changing
> the HPSUSAN without ssconfig be illegal after 1/1/11?
>
> Mike.
>
>
>
> John Lee wrote:
> > I think you're referring to copies of proprietary HP software that
> > we're illegally copied and distributed. They no doubt
> still exist but
> > we need a legal opinion as to whether or not the copyright expires
> > when support is abandoned.
> >
> > John Lee
> >
> >
> > At 01:39 PM 9/24/10 -0500, Michael wrote:
> >> I recall that someone NON-HP, had developed a utility to
> modify the
> >> HPSUSAN and CPU string, does that ring a bell with anyone?
> >> I have a client in the position where they want to
> continue with the
> >> HP3000, but their software is coded to a specific HPSUSAN, and the
> >> software vendor is no longer in business.
> >> They have a small HP3000 and would like to go up to
> something like a
> >> 9x9 with a discarray. Is there a support company that can
> help with
> >> the HPSUSAN problem, or should they look for a non HP3000 solution?
> >>
> >> IMHO: If you are a software vendor with HPSUSAN coded
> software, and
> >> you decide to get out of the 3K business, then you should
> release a
> >> non HPSUSAN version of your software to your remaining
> customer base,
> >> before you completely go out, or release your source to another
> >> support company.
> >>
> >> Mike.
> >>
> >>
> >>
> >> Mike Hornsby wrote:
> >>> First, some correction in terms: '3rd party' as applied to HP3000
> >>> services needs to be redefined. The 1st party, namely HP, as of
> >>> 1/1/11 will no longer be part of the picture. So, lets be
> honest and
> >>> just drop the 3rd party connotation and go with HP3000 Services.
> >>>
> http://www.hp.com/products1/evolution/e3000/news_events/discon
> t/operating_systems.html?jumpid=reg_R1002_USEN
> >>>
> >>>
> >>> The primary consideration for HP3000 service agreements
> would be the
> >>> cost of downtime. If the system can be down for more than a week,
> >>> then you probably don't need a service agreement. If on the other
> >>> hand, downtime does impact negatively on the bottom line, and/or
> >>> your prospects of staying employed, then support costs become a
> >>> simple business equation. A good article on calculating the true
> >>> cost of downtime is at:
> >>> http://articles.techrepublic.com.com/5100-10878_11-1038783.html
> >>>
> >>> The simple fact is that even the newest HP3000s are a decade old.
> >>> The average age of in-production HP3000s is about 15
> years, and many
> >>> are 20+ years old! The MPE/iX OS and Image/SQL DBMS code is also
> >>> very old. It is quite stunning to see: COPYRIGHT 1976
> when running
> >>> Query, or Copyright 1987 when running DBUTIL or SYSGEN.
> >>>
> >>> IMHO, the top 3 criteria for _Software Support_ service
> for HP3000
> >>> systems should be:
> >>>
> >>> 1. HPSUSAN reliant applications. Many HP3000 non HP software
> >>> products are coded to a specific HPSUSAN. If your system
> motherboard
> >>> or processor is replaced this variable will change, and this
> >>> software will no longer execute. What is your service provider
> >>> solution to this issue? In the past HP would recode the
> HPSUSAN for
> >>> a fee, but it is unclear as to what they will do after 1/1/11. If
> >>> your service provider states that they will pay HP, then
> you should
> >>> get something in writing from your local HP office that confirms
> >>> that they will be continuing to perform this service. Many of the
> >>> companies that produced these HPSUSAN coded software
> products have
> >>> gone out of business, or discontinued the software, so license
> >>> transfers to a new HPSUSAN number is not an option.
> >>>
> >>> 2. New Critical Patches. Does your provider have a
> license for the
> >>> MPE/iX source code? Will they be investigating and repairing any
> >>> critical OS, security, or network problems? WITHOUT
> PATCHES TO ANY
> >>> NEW PROBLEMS YOU COULD FIND ONE DAY THAT YOU ARE DEAD IN
> THE WATER.
> >>> This happened to some users of older COGNOS products who
> found that
> >>> the software stopped working due to hard coded end of
> service dates.
> >>>
> >>> 3. Crash Dump and boot failure assistance. Do they have
> experts at
> >>> analyzing crash dumps, machine checks, and PIMINFO data. Do they
> >>> have custom DEBUG SAT and DAT macros? THE WORST CASE HP3000_
> >>> SOFTWARE_ SCENARIOS ARE THE INSTANCES WHERE MPE/iX FAILS TO BOOT
> >>> EVEN AFTER THE SYSTEM HAS BEEN 100% REPLACED. A simple example of
> >>> this boot failure is a bug that HP introduced with
> NMLOGMON. If the
> >>> system ran out of disc space, NMLOGMON would hang waiting
> for space
> >>> to be freed up. Unfortunately, NMLOGMON also runs in the
> critical
> >>> path at boot up.Thus if the system ran out of disc space and
> >>> aborted, (a common problem) then NMLOGMON would hang on boot.
> >>> Without a patch to change permanent allocation on ldev 1,
> the only
> >>> other recourse would be an install and reload.
> >>>
> >>> The HP3000 is truly a remarkable server that continues to deliver
> >>> mission critical highly customized applications. We are
> committed to
> >>> providing the highest quality services for as long as our
> customers
> >>> need to run their applications.
> >>>
> >>> Questions or comments can be sent to:
> >>>
> >>> Mike Hornsby
> >>> CTO/CoFounder
> >>> Beechglen Development Inc.
> >>> [log in to unmask]
> >>> 513-457-5100
> >>>
> >>>
> >>>
> >>>
> >>> * To join/leave the list, search archives, change list settings, *
> >>> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >>
> >> * To join/leave the list, search archives, change list settings, *
> >> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >>
> >>
> >>
> >> --
> >> Internal Virus Database is out-of-date.
> >> Checked by AVG. Version: 7.5.560 / Virus Database:
> 270.12.26/2116 -
> >> Release Date: 5/15/09 6:16 AM
> >
> > * To join/leave the list, search archives, change list settings, *
> > * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> >
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
