[4463] in sapr3-soft
Re: Which Operating System
daemon@ATHENA.MIT.EDU (cbbrowne@news.isp.giganews.com (Ch)
Tue Jan 4 10:05:12 2000
To: sapr3-soft@MIT.EDU
Date: 4 Jan 2000 08:51:03 -0600
From: cbbrowne@news.isp.giganews.com (Christopher Browne) (by way of SAP Moderator <cbbrowne@news.isp.giganews.com>)
Message-Id: <84t1cn$739@nexus.netconcepts.com>
I've worked with SAP on UNIX for quite a few years; it would require
that you have a "UNIX guy," but the major issues in system management
tend to be on the R/3 Basis side, which *effectively* means that what
you're deciding at this point is between:
a) Training/hiring an AS/400 R/3 Basis specialist.
This is probably the rarest variation of the three, thus meaning
you may have to work harder to retain knowledgeable staff.
b) Training/hiring a UNIX R/3 Basis specialist.
There's lots of UNIX folk out there, which means that it ought not
to be *too* challenging to staff this position.
c) Training/hiring an NT R/3 Basis specialist.
Moreso than with UNIX, "MCSEs" are a dime a dozen, meaning that
staffing the position should be fairly straightforward.
Big beware: Assuming things like "NT has a GUI and is
``user-friendly,'' and so R/3 on NT will be simple, and we can drop in
any old NT administrator" is a terribly *bad* idea. R/3 is a complex
application, and the complexity is not particularly associated with
the OS.
--
"Besides, I think [Slackware] sounds better than 'Microsoft,' don't
you?" -- Patrick Volkerding
cbbrowne@ntlug.org- <http://www.ntlug.org/~cbbrowne/sap.html>
