An irreverent look at life with IBM's midrange computers for the last 25 years
I was born into the retail lumber business. My family had been in the business for nearly 30 years when I was born. I started working in the lumber yard when I was in the 4th grade (a stunning image of which accompanies this blog). Over the years I did many things at the lumber yard, although most of my earlier years were spent learning about guns, girls, and cussing from one of my earliest mentors, the lumber yard's shop foreman (there was an interesting collection of female "documentation" in his shop).
In the late 70s, the lumber yard got its first computer (using the word loosely). It was an Olivetti posting machine with a mechanical ledger card feeder that had a dual 8" diskette drive attached. It looked like the Farfisa organ that Susan Dey played in the Partridge Family. The Olivetti machine used a weird assembler dialect and, after many late nights and the mentoring skills of a local guy named John York, I learned how to program it. I was quickly hooked.
After a year of so with the Olivetti the lumber yard and I each learned one thing: The lumber yard learned it needed a real computer. We needed more business information than an Italian posting machine and Wilson-Jones 13 column spreadsheets could provide. I learned that I needed to move my career in a computer direction. Selling plywood was boring before computers; after computers it was intolerable.
In 1979 the lumber yard graduated to an IBM S/34. We bought what we thought was a good software package. I didn't know much about software, but it seemed a little lame to me that none of the data entry was validated interactively. Rather, "proof" reports had to be run iteratively until, after corrections, the numbers finally balanced. Our "package" turned out to be nothing but a bunch of DFUs strung together with a couple of menus.
It quickly dawned on me that we had a capable computer and really bad software. I rolled up my sleeves and started digging into RPG. I didn't know anything about what I was doing but it was my good luck to have a really good Systems Engineer (Dave Heminger from Fort Wayne) assigned to our account. Back in those days, a salesperson and a Systems Engineer were assigned to IBM accounts. These guys came by nearly every couple of weeks or so to buy lunch (has anyone had IBM buy lunch in the last 20 years!) and answer questions. Dave was patient and always took the time to answer my questions. I'd work for a couple of weeks and keep track of everything I needed to ask him the next time I'd see him. I vividly remember how hard he had to work to make me understand the difference between the enter key and the field exit key. I'm not a rocket scientist now, but I must have been dumber than a sack of hammers back then!
It's no wonder that IBM had financial issues and needed Lou to clean house. Those IBMers spent a lot of time at the lumber yard and didn't make IBM much money doing it. It's understandable that IBM had to change its sales model, but it's a shame that Lou wasn't able to craft a plan somewhere between the nearly full-time hand-holding we got back in those days and the nearly laughable telesales support that's offered today.
I'm nearly certain that the current state of IBM's sales force is why the AS/400 has morphed into the i5. They've never been able to even spell "AS/400," let alone sell it or explain it. "iSeries" came no easier. I think an IBM bean counter threw up her arms in frustration and said, "Screw it! Let's name it 'i5' and see if they can spell that!" Ten bucks says that initiative doesn't work and when you say "i5," the crack IBM telephone salespeople today think you're saying "I 5." As in ask my two-year-old daughter how old she is and she says, "I 2."
I'm grateful to both John York and Dave Heminger. Without their help, I'd probably be selling plywood at Home Depot today, live in a double-wide down by the river, and have a serious drinking problem.
What's your story? Where did you get your start? What, and who, put you on the path to IBM S/3x midrange machines (and their follow-ons)?
rp
Coming soon: The glory of WSU.
Posted by rpence on January 26, 2007 at 11:47 AM | Comments (17) | TrackBack
25 years isn't really all that long in the grand scheme of things. There are pyramids that are more than 4000 years old for cryin' out loud! However, considering that the lifecycle for most things computer-related is often less than that of a mayfly, 25 years is a really long time. Over the course of the last 25 years, many of us have spent nearly all that time watching, using, buying, cussing, programming, praising, learning, castigating, selling, and upgrading IBM midrange computers.
Even though the last 25 years are only about .6% of the life of an old pyramid, for many of us those 25 years represent a substantial portion of our computing careers. During that time we've used S/34s and S/36s; computers that were the entry point into computing for many of us. We've used S/38s and AS/400s; computers that propelled many of us into the world of "serious" computing. We've watched the AS/400 morph from a proprietary, almost specialized, platform into an open, powerful machine. And we've seen it go through more name changes than Puff Daddy (or is just Diddy now?).
To commemorate the 25th anniversary of System iNetwork, I'll blog here about life and memories over the past 25 years in the midrange community. In the course of those 25 years, I'm proud to say I've been there in the thick and thin of much of it. I've coded a lot of RPG in that time, written many articles, given many seminars, and worked with and for many IBM midrange shops for a variety of projects. Over the course of the next six months or so, I'll blog about what the last 25 years have meant to our community, our history, our story, our life, and our careers. And so we don't sound like a bunch of reminiscing-only, "those were the good-ol' days" types, we'll occasionally try to apply lessons from the past to help us do a better job today.
We'll discuss topics that include RPG, IBM, OCL, CL, where we got our start, where we're headed, our most pathological RPG coding techniques over the years, things IBM's done right, things IBM's done wrong, Shelly Cashman (ring a bell?), SOM/DSOM, whatever happened to...(am I the only one who remembers Dave the Traveling programmer?), Carson Soule's Revenge of the Indicators, "word processors" for the S/34, folding coding templates, COMMON (and favorite--with names redacted!--CUDS stories), Windows, Netware, MRT programs, OS/2, Taligent and Pink, AD Cycle, Indicator L0, IBM 5150 terminals, and whatever other esoteric memories we can dig up.
The floor is open and short of you calling my mother ugly, your comments will be posted. So please participate. This blog isn't about me blathering about what I remember; it's about us (blathering about what we remember!).
Later this week, the first post (posted in a few days) will be about getting our feet wet with the IBM midrange. Can you remember when you struggled with the difference between the enter key and the field exit key? I can!
rp
Posted by rpence on January 24, 2007 at 12:13 AM | Comments (11) | TrackBack
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
We welcome your comments and opinions and encourage lively debate on the issues. However, Penton Media reserves the right to delete or move any content that it may determine, in its sole discretion, violates or may violate its Terms of Use or is otherwise unacceptable. For more information, see Penton Media's Terms of Use.