HP3000-L Archives

January 2000, Week 1

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:
Bob Walker <[log in to unmask]>
Reply To:
Date:
Wed, 5 Jan 2000 10:12:38 PST8PDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
This thread brings a similar issue to mind.

There seems to be a variety of reasons that management can
come up with for moving from HP3000 to NT.
The one I have to contend with is:

'There is little expertise out there in HP3000 systems. If you got hit
by a bus, we would have a hard time hiring someone off the street
that could come in and quickly assume control of the HP3000
system and databases, therefore we want to a move to platform
where we can readily hire replacements if need be.'

If I may impose, to those who have the inclination, how would you
answer this in a reasoned manner?
Answer's like 'That's absurd!', although true, are not really useful.

Environment:
1 HP3000 - 939  100 user license. MPE 5.5 Xpress 7 + patches.
   Image/SQL and Client/Server very active.
   Apache heavily used.
   Samba.
Support:
1 - me. about 10% of my time spent on systems(updates, patches,
backups, id creation). Not much time spent, but when needed, it's
fairly complicated, that is, latest patches and revisions of everthing.
1 - backup to me. Less expertise, used to be system manager
years ago.

Location:
Vancouver, BC, Canada.

Thanks to any that can give advice.
Bob.
--=--=--
Bob Walker, Computer Centre  --  [log in to unmask]
Capilano College, North Vancouver, BC, CANADA.
------
'No one is listening until you make a mistake.'

ATOM RSS1 RSS2