This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I'm suprised we haven't seen some passionate replies yet!
A few years ago IBM consolidated their servers under the eServer "brand," thus the s390 became the zSeries, RS/6000 became the pSeries, etc. The AS/400 became the iSeries. IBM marketing running amuck, adding their usual amount of value. Whoops, that was an editorial. Anyway, you can find out more at http://www-1.ibm.com/servers/eserver/iseries/
I'm a s/w guy, not a h/w guy, but still I think the iseries architecture is tops, and there are a zillion stories about customers who actually have forgotten where their server was located, due to its reliability.
Its a whole new hardware (AS/400) with its OS (OS/400), supporting database (DB2/400) and languages (CLP/400, RPG/400, COBOL/400). The name 400 sticks because they machines (mid-range machines or i-series machines) were thought to be ble to support 400 concurrent users at any time.
I developed on AS400's for 10+ years before moving to the wonderful world of Java/J2EE.
It was green screen terminals and a big AS400 server, strangely similar to "thin Client" but not as pretty.
There were some differences, everything worked straight off, no classpath/configuration nightmares, what you knew last year was still worth knowing the next. Everything didn't start with a J. What there was to learn was delivered in about 30 manuals with the box and they weren't full of typos! We even had time to concentrate on the business logic and write some pretty big systems Twas awful
Only downside was being locked into IBM.
I really like Java (despite my digs) but the old proprietary stuff had some strong virtues.
There were some differences, everything worked straight off, no classpath/configuration nightmares
What about library list nightmares
Everything didn't start with a J.
But everything start with Q for example QAQQINI is really terrible name
I'm really new to AS400 and I feel it very hard to learn.
SCJP<br />SCWCD <br />ICSD(286)<br />MCP 70-216
Joined: Sep 22, 2003
You have a point David
Although at least with library lists it just looks in that list and if it aint there thats it. No funnies like stuff relative to context roots, classloaders inheritng from other class loaders Web App funnies depnding on whether your in out (shake it all about) of a JSP or who wrote it IBM, Oracle, JBoss my Auntie.
Now I look back on it (albeit with rose tinted specs) a lot of things did begin with Q QBatch, QUser and all the low level API's.
Bet I could still drive an AS400 though even if it is 5 years ago
I had the advantage of a long course (12 weeks) on AS400 to help.