HP3000-L Archives

April 2000, 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:
"Glenn J. Koster, Sr." <[log in to unmask]>
Reply To:
Glenn J. Koster, Sr.
Date:
Wed, 26 Apr 2000 06:31:35 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Frank,

It depends on a number of factors.

1.  Price...  obviously this is a prime consideration for most folks.  If they don't
     have or can't afford a 3000 of their own, price becomes number one.  

2.  Availability...  How will scheduled downtimes impact availability.  Will the 
     machine be available at any point for exclusive use (yes, there are some
     development projects where you want to be able to test where you know
     if you crash a machine you won't impact other people.

3.  Location...  Many of the classes that need to be developed for the 3000
     need to be developed with a "hands on" approach for lab work... especially
     the system admin courses (ties into exclusivity also).  If the machine is
     located in Texas, it wouldn't benefit someone in Iowa that much for these
     types of needs.

Just some thoughts to pass your way.  Once you open your machine to others
you will have to address these kinds of questions one way or another.  I am
speaking from experience because I used to be the data center manager for
an HP 3000 service bureau back in the late 70's called DataBase, Inc. out of
Grand Rapids, Michigan.

Glenn J. Koster, Sr.
Managed Business Solutions, Inc.
Under contract to Hewlett-Packard and Agilent Technologies
(316) 549-3622

ATOM RSS1 RSS2