• Subject: Don't Blame The Hardware
  • From: Bob Larkin <blarkin@xxxxxx>
  • Date: Wed, 15 Jul 1998 23:46:11 -0700

The July 13th Corporate Strategies article would seem to indicate that
the AS/400 was the cause of all the problems at the construction company
featured in the article.

What is most interesting is that the software is defined as 10-15 years
old. If this is truly the case, what operating system was it designed
for? Since the AS/400 hardware and OS/400 operating system are only ten
years old, it must have been designed for another system. The article
made reference to flat, unconnected files. Since the AS/400 , and it's
predecessor, the Sysyrm/38,  have had built in database support (fully
realational for the AS/400, the application was probably written for the
System/36.

Couple an ancient application with a staff that was probably given no
resources for training, or enhancing the system, and you end up with an
antiquated piece of junk. Now management wants NT, so they buy new
hardware. This sounds fairly stupid, siince the AS/400 will run NT, and
is more reliable than the currently available PC hardware.

All in all, it sounds like an attempt to cover up poor management,

Bob Larkin
Consultant
Houston, Tx
(713)7890-9552

begin:          vcard
fn:             Bob Larkin
n:              Larkin;Bob
org:            <A HREF="HTTP://web.wt.net/~blarkin/">Larkin Computer Consulting</A>
adr:            <A HREF="http://web.wt.net/~blarkin/">Bob and Diana's Page</A>;;;Houston;TX;<A HREF="http://web.wt.net/~blarkin/">;United States
email;internet: blarkin@wt.net
title:          Systems Consultant
x-mozilla-cpt:  ;4104
x-mozilla-html: FALSE
version:        2.1
end:            vcard


This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].