Slashdot Mirror
Selling Linux to AS/400 Shops?
cgh4be asks: "I work for an IBM business partner and each year we host a technology seminar for our customers, most of which have AS/400 backgrounds. I am the 'Linux guy' at work and have been chosen to give a 1 hour presentation to these IBMers about linux. So, my question to the Slashdot community is, what points and information should I touch on in this presentation to make it effective? I'd like to give some history about it of course, but the goal is to get them to start using it in their businesses."
My question is: why?
AS/400 are decent machines with a good operating system. It has the virtue to "just work". I'm not really sure you would want to replace an AS/400 with a Linux box. The AS/400 is -after all- a proven and stable platform.
I'm all for Linux, but not in this category of hardware.
You must believe that Linux is a better choice for some reason. You're going to tell them that this young, haphazardly developed, upstart OS is a better choice than a mature, thoroughly architected, industry standard OS.
I think you'd better tell us, rather than the other way around.
I have been pwned because my
AS/400 units are database servers. Sure, you can get an web server, and a firewall on the unit, but they all run out of a database anyway. The neat feature of AS/400 units that I like is I can ftp to a directory, and upload files, and they are added to the database.
Linux is much better in the other services that AS/400 units don't cover very well, but that they can cover. Such as firewalls, mail servers, file servers, and they could be used as a way to interoperate with winblows... oh, don't forget... if you get db2 for linux, you can run your database on linux and do an offsite remote sync up.
In addition to many of the good recommendations you are getting below I'd recommend:
Unix for the Mainframer
While this is more directed at MVS and not OS/400 the first chapter could end essentially being your 1 hour talk. A great example is the difference in Unix speak between: command, script and application. The underlying philosophy here is one of an interactive environment where small non-job specific programs (commands) are put together for job specific tasks (scripts) and that these are distinguished from customizing large systems (applications). Just explaining the pros and cons of this model will be insightful and will take up a good deal of time.
Incidentally in terms of the cons as a Unix guy you may not have thought about these. Here is a pretty good anti-Unix pro mainframe article which will help you see the other side S390 vs. Unix servers.
Anyway hope this helps