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.
It would be useful (I think) to focus on how Linux with IBM solutions would compliment their existing AS/400 architecture. It's not generally a great idea to suggest that they scrap their existing applications and move wholesale to another OS or hardware platform.
The bottom line that they'll want to know is if it can save them money while offering an equivalent or (preferable) better service to themselves or their customers.
Focus on integration, scalability, flexibility and IBM's commitment to supporting the Linux arena.
Better the pride that resides in a Citizen of the world, than the pride that divides when a colourful rag is unfurled
Our AS400 systems were very impressive-looking in a "I AM BORG" type way. They had great reliability and service, but they were older models, expensive to maintain, and didn't have very good performance. I suspect other shops are in the same boat.
:)
We started using Linux machines as development platforms. The AS400 guys could run db2 and other IBM technologies on Linux, which was a big win. The development stations were dirt cheap and for many jobs faster than the AS400.
Eventually as that department became more comfortable with Linux they stopped placing every business application on the AS400s if a properly configured Intel/Linux box could do a cheaper/faster job without unacceptable risk exposure. It turned out quite a few applications fell into that category.
The key is to have someone who has a deep understanding of linux and also can talk to the hardcore "mainframe" admins. There is definitely a culture shock to overcome. Imagine trying to explain Linux to someone who calls service for any task that might require opening a box, pays 10k/year license fees for a glorified tar backup system, and knows so many esoteric commands and proprietary-os arcana to make VAX and UNIX together look like kiddie toys.
On a separate note, I don't think it makes a lot of sense YET to run Linux ON the iSeries. The DASD is extremely expensive, and you could run a much larger system for less money on normal PC hardware. That being said, I have heard that Linux is now the firewall of choice on iSeries, so you may want to do some research on iSeries Linux applications.
Good luck on your presentation.
- Kurt Schroeder
Interesting...can you explain this a bit more to those of us who've never seen an AS/400 in operation? After I upload a file and it's added to a database (a db2 database or some other hidden format?) is it queryable? Can I somehow "select uloaded files from sometable where upload_date between $thisdate and $thatdate" ?
:))
I know that Microsoft is planning to dramatically integrate database functions into the filesystem in an upcoming version of windows (Longhorn? Yukon? I forget)...but it seems that once again MS is not the innovators, that maybe someone did it long before them
Our AS/400s are actually new. The oldest one is only a year old. For us, despite our deep Unix and NT backgroud, Linux on an iSeries (there, I said it... the new name... blech) holds little more than sideshow value. For us, we have almost no investment in AS/400 admins or developers. We just add HP/Compaq servers if we want more Linux.
/400 shop. Someone like our parent company that has AS/400s everywhere (30+) probably sees a huge benefit to running several Linux virtual servers on an LPAR* or older single system. The key to stress is reuse of older systems. Some of the first generation RISC systems (F10s and the like) would make great highly-available Linux machines.
However...
We aren't a typical
What's more, a company with a large investment in the hardware has probably moved all but some development off of a depreciated system. The shops that have two systems still running V3R7 won't be interested.
Part of the problem is that IBM doesn't really push economical LPAR-ing for Linux up front. In our case, they said "Sell you on LPAR? Well, if you aren't interested, we can't change your mind." Really, the Rochester salespeople are technically very knowedgeable, but they just don't "sell" sometimes. And, I can't go back and get the money now to do an LPAR "just for Linux".
The other issue is that IBM (to date, anyway) doesn't push AS/400 to SAN connectivity, which increases the value of the AS/400 as the key system in your enterprise whether you run Linux on an LPAR or not. You could, in theory, run a fairly-sized enterprise with a handful of 8xx-series machines. You'd have an NT-based FSIOP (or Novell, if you swing that way) if you had a need for it. You'd LPAR a big box to carve out several virtual Linux machines to keep your development options open. And, you'd have great MTBF on the hardware (except for the problems with the 17GB drives... those die like flies). Back all of that with an enterpise-class SAN (Shark, EMC... no Hitachi or HP XP-series because they don't support the 520-byte block size), and you can snap whole systems from LPAR to LPAR and system to system. Then, you can use a CNT-like solution for data replication over IP to a disater recovery site because all your data is on your SAN.
Sorry for the ramble, but I guess the point is that making the case for Linux on an AS/400 is part of a big picture. I'd say the cost-savings of having a handful of the same hardware in your computer room but the flexibility to run virtually any application is an outstanding point.
* LPAR == Logical PARtition... it's similar to how a Sun E10k can be carved into separate systems at the hardware level. And, yes, lots of other companies have done the same thing. It's not new.
Amateurs discuss tactics. Professionals discuss logistics.
Why? Try tested, reliabile 24/7 uptime for mission critical applications. We use as/400 at my hospital for storing patient admission data, among other things. The command system is archaic, but it works, and it is extremely reliable.
It's just what you are used to, what matters. I'd probably select a *BSD solution for any problem I get to solve because I'm a *BSD guy. You prefer Windows or Linux? Great...you'll probably choose that.
Beside, one large point people tend to forget is that AS/400 are used in enterprises, often with custom-made applications. The worth of the machine is mostly in those custom-made applications that matured over years and years. Porting those is either expensive or a titanesque task.
And honestly? Do you think "ps -auxw" is anything less cryptic than the example you gave. If you answer me "yes", you are just biased because you have issued that command a million times. Try to think back to the day you first issued it and thought how neat it was....
Sorry, but it is impossible to pass judgement on OS/400 if you have no experience with it. It's a COMPLETELY different way of thinking about operating systems, and it's simply not comparable with Unix or Windows. I come from a Linux/Windows background, and I'm still trying to get my head around the /400 mindset after working with it for a few months. Oh, and the filesystem you don't like? It's DB/2. Think about how cool that is for a minute. It's easy to look at something different and immediately dismiss it as *wrong*, but we don't have that sort of ignorance here on Slashdot...right? ...right?
Okay, my posts here are starting to sound like trolls, but I'm going to keep working at this point.
I've heard about a lot of systems billed as being "reliable". Windows folks call Windows 2k "reliable" and say they never have a problem with their servers, that they've been up for months. Linux folks call Linux more reliable than Windows, and say the same thing about their servers. Ditto for the BSD guys, the Sun guys, and evidently for the IBM guys.
So here's what I want to know -- I'll give you that the system is reliable, but that's only meaningful in the presence of unreliable alternatives. Are you claiming that an AS/400 box running OS/400 is more reliable than a BSD box, or a Solaris box, or a Linux box? I've never seen any of these just spontaneously fail or kernel panic...
May we never see th
Specialization, specialization, specialization.
Oh. And reliability.
So four words.
I cannot begin to describe how bullet-proof an AS/400 is. People simply don't believe me. One poster said that he knows people who IPL once a year. That's probably because it's *intended,* by the way - not because the machine hiccups. These suckers are the equivalent of cockroaches - they'll survive a nuclear blast.
But other than reliability, you're going to have to go after custom software markets. And not the glamorous stuff - the boring flat database stuff. I work for a good-sized printing company. We used an industry-specific ERP on an AS/400 for years and years. We still use that same app - only we now use the Windows version.
The AS/400 version was far less maintenance than the Windows version for various reasons - but the bottom line is the specialization. This isn't a couple of spreadsheets and a bar code wand out on the shop floor. This is much more involved than that and my industry type isn't the only place where this kind of software shows up. At the AS/400 mini-conferences I attended there were casino IT people, tool and die shops - even the car dealer I frequent has an AS/400 running industry-specific parts-tracking and job estimating software.
Plus these are not necessarily companies that have large R and D or programming departments. Nor *should* they. There are a lot of companies that are similar in size to ours that have IT people, a geek or two, but no one that really has the time, wherewithal or desire to replicate industry specfic software that can be easily purchased (for around $20,000 for all of the modules in our app) and supported (for about $2,000 a year.) Yeah, the hardware is expensive, but so is my time or the time of a programmer to create something that is customized for us. And oddly enough, I do have other things to do...
If you were selling Linux to me as a replacement for an AS/400, I'd first ask you what software is out there that will run my kind of manufacturing plant. I've already been down the "take some general software and customize it" road. It's a dead end.
If the answer is that I have to hire someone to write it or come up with something on my own or that you'll gladly look into consulting with my company on our specific needs, I'll hang on to my Black Beast, thankyouverymuch.
Consigned to flames of woe.
Do you think "ps -auxw" is anything less cryptic than the example you gave.
You make a good point -- I do take this for granted. However, this is also one of the more cryptic UNIX commands. Hmm. I think I should rephrase this. There are a lot of UNIX admins running around (compared to OS/400), so for better or for worse, a Solaris guy can get along pretty well on Linux. The commands are well-known by quite a few people.
On OS/400, however, the situation is worse, even assuming an equivalent level of "crypticness" because many people have to learn the OS for the first time.
The obvious attack against me is "Well, there are more MCSEs than UNIX admins, so UNIX also takes a penalty for being cryptic." I *agree* with this -- but UNIX is also being quite accomodating (because it has to be) to that majority of users, making available to them Windows-like environments like GNOME, and GUI administrative tools.
So OS/400 should have to do *more* work to be appealing to the average admin than Windows or even UNIX does...and it doesn't seem to be that it does.
Finally, I stand by my complaint that the programming environment is less than impressive -- the languages are really old. OS/400 programmers *might* just have have a deep love for COBOL or something, but it would really frusterate me.
You are right about the legacy custom apps, but that doesn't excite me about OS/400 -- it just makes me think "People *have* to use OS/400" rather than that "People *want* to use OS/400". It's the same frusteration I see when someone's written something for Win32 or the MacOS that I'd like to use on UNIX (or, occasionally, some other variant of UNIX).
May we never see th
Sorry, but it is impossible to pass judgement on OS/400 if you have no experience with it. It's a COMPLETELY different way of thinking about operating systems, and it's simply not comparable with Unix or Windows.
/400 mindset after working with it for a few months.
/400 is *not* all that accessable to most people.
...we don't have that sort of ignorance here on Slashdot...right? ...right?
:-)
Fair enough.
I come from a Linux/Windows background, and I'm still trying to get my head around the
That statement, though, also illustrates what I'm frusterated with.
Also, there's plenty of good documentation and help for UNIX systems available on the Internet -- this is not true (unless I'm missing something) for OS/400.
It's ignorance that gives us conversations. If we already all knew everything, there'd be no point in talking to each other -- Slashdot wouldn't exist.
May we never see th
I'm in a similar position. I've recently started a new AS/400 job and am trying to make my fellow IT workers aware of Open Source. I've used the IBM mid range since the mid 80s and Linux since '97.
It all depends on your target audience.
If it's AS/400 techies then show them X apps running on the AS/400 with remote Xterms. Show them a small beowulf running on one Iseries. Show them DB/2 on Linux seemlessly intergrated with DB/2 on the AS/400 etc etc _Show_ them tech.
If it's manager then comapre it to Windows, do not threaten the AS/400 that's a losing battle in their minds. Tell them about support, costs, stability availabilty of staff, lack of lock in etc. You could then go on to talk about consilidation on the AS/400. Most AS/400 people love the machine it's simple to program and operate. Linux cannot win that battle, programming on Linux is hard by comparison.
In short it's a hard sell. Most AS/400 shops have AS/400 and Windows skills. The closest you'll find to unix skills is the network admin who last touched AIX in '94.
It will take another 2 years before we'll know if AS/400 users are going to embrace Linux. I would love to run Linux in my company with a bunch of Xterms rather than PCs. It would save the company $$$
Some of the (very little) bit of documentation on OS/400 that I could find on the Internet implied this -- not that one had to keep commands upper case, but that the system did so automatically. I'm used to an OS that distinguishes between case in commands, so this is a bit of a drawback for me.
I could be wrong -- this is some of the only OS/400 documentation that I could *find* freely available. It was a chapter excerpted from a book.
I was kind of interested in learning about OS/400, so I wanted to read up a bit about it. There was very little freely available information, though. This was terribly frusterating to me, because there's plenty of UNIX information available on the Internet.
I hold IBM somewhat responsible for this -- it costs them very little to give out information to the Internet at large, and yet they do not do so. Unless you're a shop prepared to drop quite a chunk of change on propriatary hardware, IBM salespeople aren't going to be very interested in giving you information -- and even if I was, I'd want my evaluation of the system to be based on my *own* interpretation of what I can read about the system, not on what I'm fed by the salespeople ("99.99% uptime! Foo Technology! IBM 24/7 support!"). Oh, yes. IBM does sell (*very expensive*) classes/seminars (oriented towards training to perform specific operations, from what I've seen) to teach people about OS/400. So if you're willing to drop quite a bit of money to learn about an OS that you may not want to use, you can get some information. However, others end up SOL. And I'm in the latter class.
May we never see th
Actually, there is this area... iSeries Information Center Entry Page
-Pete "Beauty within, forever bright; illuminating, the darkest night."
Who's talking about replacing the AS/400 with Linux? You can run Linux right on an AS/400 now. You can run a Linux webserver right inside the box, directly connected to your DB2 database or whatever legacy application or data you want to serve. You can run an additional Linux firewall to protect access to both your webserver and your AS/400. These Linux servers can also be backed up right along with your AS/400 and if necessary restored completely with a single command. You can develop your Linux applications on an Intel desktop and drag and drop them right onto the AS/400, ready to use.
/ linux /
The base operating system of the AS/400 is case insensitive, the commands are printed in all caps in the documentation so that they can be easily recognized. However the AS/400 recognizes multiple file systems including case-sensitive ones. You can even design your own if you like.
If you're hooked on Unix commands try typing QSH on an AS/400 command line and you will find yourself in a Unix environment.
AS/400 are rock solid machines. Our three systems (consolidated from 6) have not been down in the four years I've been here, through three disk failures(hot swap replaced) and a complete power outage of the data center.
You can purchase a bare-bones AS/400 (iSeries) for about $7K. That said, a system like that won't get you much further than your average Intel box, but they scale up rapidly. For the $20K mentioned you can get a fairly good performing system. If money is no object you can spend $1M+ on a 32-way system capable of running 128(or more) virtual linux servers.
For iSeries (AS/400) info try:
http://www.as400.ibm.com/
or better yet:
http://www.as400service.ibm.com/
For Linux on iSeries go to:
http://www-1.ibm.com/servers/eserver/iseries
Scott Ingvaldson
WRKSYSCTX is "work within the system context"?
WRK = work
SYS = system
CTX = context
All of the OS/400 commands are like this. Three character 'words' combined in strings of one, two, or three 'words' as in your example.
There were exceptions. WRKSPLF for example,
WRK = work
SPL = spool
F = file
Note that WRK is always work. This is true for all of the three character codes. This made the commands easy to learn and remember. Contrast with *nix, where each command name has to be learned separately.
And it is not in condensed combinations of verbs, it is verb noun modifier.
As to the all caps requirement, are you sure that wasn't just a convention in the document you were reading to distinguish commands from the other text? OS/400 has no such restriction.
Steve M
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
> Also, there's plenty of good documentation and help for UNIX systems available on the Internet --
> this is not true (unless I'm missing something) for OS/400.
You're missing something: redbooks at IBM
1) wasting time covering things they already know, or
2) hitting an open wound and pissing someone off.(... or both)
What they called you in for is to know what Linux can do for them. If you really want to impress them, I'd say try and be candid. Say both what it can do, and what you should not (currently) be used for (I'm sure there's a few of those).
If it was me, I'd start with a quick history of Unix/Linux.. how Unix was Pseudo-Open Source in it's early days and how the closing down of Unix led to the founding of the GNU foundation which opened up the way for Linus to write a kernel with the promise of all those GNU utilities to populate the hard disk.
I'd probably cover off a couple of the popular OS licenses (GNU & BSD at the least).. Let them know the downfall of the GNU license (Don't canibalize the source unless you want to free your own), and the advantages (everybody is a potential support person).
At that point, you could probably go through a quick Hall of OS fame (Sendmail, GCC, SSH, Apache, MySql/Postgres, Perl, The Web.... [Remember that Microsoft is Still using BSD code in NT's TCP stack, and IE started out as the Mosaic web browser]).
Some other things you might go through are stability, ease of use/installation (network installs are the way to go, and faster than CDs) and, of course, the ability to fix almost anything that you really want to fix -- or farm it out to someone else (distributer) if you've got more money than time.
The next thing I can think of is to do a quick overview of some of the various Linux distributions available -- big ones, little ones; general ones, specific ones.. If nothing else, it shows off how you you can customize Linux for anything from word processing to firewalls.
After that, you might mention a couple of areas where you see Linux as a possible boon directly within the company (probably underlaying why they really want to hear from you).
Free Software: Like love, it grows best when given away.
To make things even easier OS/400 gives you an abundance of assistance with command parameters. Type in a command and press F4 and you are then prompted with all possible parameters for the command. And the parameter explanations are written in plain english. The F4 trick works from anywhere, even within system utilities. If you need to change a setting, but don't know what options are available, hit F4 for a list. If you hit F4 on a blank command line, you will be given a menu that helps you find the utility you need. Very helpful.
In addition, OS/400 has better online help than any operating system ever. If you type in a command and hit F1, you get detailed help for that command, written in plain, easy to understand english. Try saying that about man pages. Also if you are in a utility and you move the cursor over to something you don't understand, press F1 and you will get help on that component of the utility. Help on OS/400 is incredibly useful.
You shouldn't dis an OS you know nothing about.