Slashdot Mirror
IBM iSeries or Windows server?
Rabid Cougar asks: "I am the network administrator for a small manufacturing company. Our current ERP system has outlived its usefulness and we are in the process of selecting another package. Our present ERP system runs on an IBM AS/400, but there are those in the company who believe we should switch to something that only runs on Windows. My position is this: if we can find software that will meet our needs that runs on an IBM iSeries (new name for the AS/400) then we'd be certifiably crazy to move over to the Windows platform. A co-worker insists there are a ton of reasons to avoid the iSeries like the plague. I'm not trying to start a flamewar, but if you were to bet your career on this issue, which side would you choose and why?"
You choice chould be swayed by security; I don't know about the new i5/OS generation, but back when it was called OS/400 it had one of the highest ratings for both security and stability of any mid-range system in its market. Whether this is because OS/400 really was more secure or just too obscure to exploit is up to personal opinion.
Qsecofr vs. root, eh?
Hilary Rosen's speech was about her love of money and her desire to roll around naked in a pile of money.
It got so bad that the processing teams actually created little pieces of card that they used as tickets to ensure that they could access workflow (web-based run on windows).
The users within SI (my dept) have told us that if we ever force them to do the same with our applications, which include DebtManager on AS/400, then we can expect to be very bruised.
To answer your question, I would point out the mass of windows problems and ask someone to show anything that has gone wrong with (insert midrange / mainframe platform here) that has caused the same effect.
Good luck.
... but it seems pretty obvious to me that there's a pretty reasonable way to solve this in a rational manner with a trade study. obviously, the more money at stake, the more time you'll have to be willing to invest in the trade study. as a rough guide:
/then/ ask again whether the iSeries or a windows based solution is better. otherwise, your choice of platform is already made for you.
1) write down the features you need in an ERP
2) find ERP packages which fit the bill
3) define appropriate metrics (cost of administration, expected amount of down time, etc.) i realize that many of these will be fairly fuzzy, but you can still get a reasonable idea. metrics should include both costs (upfront and maintence / tco type estimates, whether you already have admins to do the job or will you have to hire, etc.) and benefits / utility
4) map out on a matrix how each ERP package performs overall
5) pick the best ERP in terms of cost/benefit
6) if the winning ERP runs on multiple hardware platforms,
personally, as i spend more time in industry, i become increasingly agnostic: i don't care if it's linux, os x, solaris, windows, vxworks, etc. — if it's the right tool for the job, then that's what i'll use. which means os x at home, linux for work, and windows for administrivia, time sheets, presentations, etc. in my case.
AS/400's are some of the lowest TCO systems on the planet. My wife worked at a place that used an AS/400 system bought in 1989... when she told me about it I laughed, until we realized that the machine had nearly a decade of uptime with about 30 users hitting it every day and no IT staff of any kind.
The machine eventually had to be rebooted when a hard disk died and the machine phoned home... an IBM guy showed up to replace it and nobody knew that there was a problem.
The system was replaced about 18 months ago (because spare parts were no longer available) by an Windows/Oracle system that is complete garbage. Bugs in the IBM eSeries lights-out-management card caused the system to reboot every 60 minutes. Things like restoring backups are also much more complicated and error prone. (On the AS/400, restoring the system from bare metal required you to insert the tape into the drive and holding down a function key)
Conformity is the jailer of freedom and enemy of growth. -JFK
Bill Gates even learned the lesson about screwing up an environment a while back whe he gave the order to replace Microsoft's 23 AS/400's with Wintel servers. He ended up with an environment of 1,250 servers that were still not as scalable as the 23 AS/400 machines. Eventually, they killed the project. In order to avoid being teased about owning AS/400's, Bill created a new company. He sold the AS/400's to the new company. He fired all of the AS/400 people working in that department, and hired them at the new company. Finally, he "outsourced" the AS/400 functions to the new company. Oh, and Microsoft threatened to sue IBM if their people ever repeated this information in public. Nope, I don't work for IBM, but I do make my living working with the iSeries product line. I don't need to go anywhere else, because IBM keeps coming up with enhancements that keep drawing customers to the platform. By the way, there are lots of ERP solutions that run on this system. Plus, it can have partitions that run guest operating systems, including the products from Microsoft.