At the risk of sounding like an AS/400 rah-rah...

...because let's face it, I am.

Here's a message I stole from the MCPressOnline forums.  I'm not going to
comment, I think it does pretty darned well all by itself.

-------
Keith,

I am in the same boat as you. I took a Unix class, but was on the 400 until
about three months ago. I don't remember much about Unix either.

Everything here is so segmented and siloed, it's ridiculous. Forget the
20,000 users. We don't have nearly as many as that, and the servers crash at
least once every week or two. AND we can't run production batch jobs until
our client service center goes down for the day, because of the negative
impact the batch jobs have on the service center screens. It's crazy to have
to stay late to run these jobs. That's what queues and schedulers were
invented for. I am taking a backwards step that I don't like.

Our 400 application supported 24 clients in production, and test. We also
had IVR and internet production and test running on the same server. No
problems whatsoever. Now we have 7 production servers, 7 replication
servers, 7 test servers, and 7 development servers. Also have two servers
dedicated to processing long running client jobs. THAT'S EFFICIENT?? I don't
even want to think about the personnel required to support that. That does
not include our network servers. AAAHHH!!

Thanks, Keith

Doug.
-----------

For those interested in the whole thread (hello Malcolm!), you can find it
here:

http://www.mcpressonline.com/mc?128@38.nU3Papa056v.111310@.6ae57658

Joe