z/OS is IBM’s flagship operating system for its mission critical z System enterprise servers. Earlier this week IBM lifted the veil on the upcoming z/OS 2.3 release, with general availability planned for September, 2017. IBM’s Early Support Program is potentially available to those z/OS licensees who can’t wait that long. (Ask “your friendly IBM representative” if you’d like to join the ESP.) The preview announcement is chock full of interesting new features. I am particularly interested in these items:

  • z/OS 2.3 will require an IBM zEC12, zBC12, or higher model machine. That’s a fairly aggressive leap forward, but in my view it’s a sensible one. Setting a higher baseline means that z/OS can do more to exploit newer instructions and other newer model features.
  • z/OS and its predecessor, OS/390, have included encryption services for decades, but this release makes encryption of data sets, zFS, and CF structures much easier to implement because there’s no need to change applications.
  • Communications Server will incorporate a network security “sanity check” (my term) feature, to warn administrators if they’re not being at least reasonably careful to encrypt network connections. (Philip Young might appreciate this new feature.)
  • z/OSMF will support a standard software installation package for z/OS, based on some recent vendor consensus. Consequently z/OSMF will support both SMP/E and non-SMP/E (but also standard) software installation.
  • z/OSMF will integrate the z/OS incident log with IBM’s support database to find likely APARs (fixes or documented workarounds) automatically.
  • XML System Services will use 64-bit address spaces, to handle larger XML documents.
  • Eight character TSO/E user IDs!
  • IBM Knowledge Center for z/OS will include a message lookup feature.
  • The Sub-Capacity Reporting Tool (SCRT) is moving into the base operating system, and IBM is opening it up to software vendors.
  • Workload Manager will have a “maximum zIIP” control (my term) that can be applied to particular service classes. WLM will require all zIIP-eligible work within these controlled service classes to execute only on zIIPs, never on general purpose engines.
  • Online migration of HFS to zFS, and online repair of zFS. (IBM expects that the z/OS release after Version 2.3 will be the last to support HFS.)
  • RACF user ID to e-mail conversion and mapping.
  • JES2 job notifications and z/OSMF event notifications via e-mail.
  • Although z/OS 2.3 will still be available on tape media, IBM says it’ll discontinue tape media deliveries of z/OS and related products in the future. Electronic delivery (Internet downloads) and DVD media will continue to be available.

IBM issued a monster product withdrawal announcement earlier this week. For the record, I’m personally not fond of how IBM announces product withdrawals. Yes, IBM typically includes a “Replacement program information” section in such announcements. However, unless the new product is a literal, exact replacement, such as a new release (and sometimes not even then), IBM will often write “No replacement.” Probably because it’s easy for the copy editor to write that, and solution architects (for example) aren’t often the ones involved in drafting these withdrawal announcements. That’s frustrating. In my view, IBM should write “No exact replacement” and, better yet, provide some more useful, solution-oriented guidance about replacement options.

Let’s look at an example or two from this particular withdrawal announcement. One of the “No replacement” products listed is Cognos Business Intelligence for z/OS (5655-Y26). Fortunately there’s no emergency. IBM standard support for that product will be available until April 30, 2018, and extended support will be available to purchase thereafter (presumably). Oddly enough, that product won’t even be withdrawn from marketing until April 30, 2018. But of course there is a superb, mainframe-hosted replacement product: Cognos Business Intelligence for Linux on z Systems. Query Management Facility (QMF) for z/OS is another potential replacement, and so is IBM Cognos Analytics on Cloud. Or some combination. “Talk to your friendly IBM representative,” but no rush.

Another example is IBM Cloud Manager with OpenStack for z Systems. “No replacement.” Actually, no, there are quite a few replacement options for ICMO. Upgrading to IBM Cloud Orchestrator is one possibility. z/VM’s Cloud Manager Appliance (CMA), a no additional charge z/VM feature, is another. Again, no emergency. IBM won’t discontinue ICMO’s standard support until April 30, 2020.

How about ACF/NCP and ACF/SSP? These are classic (some would say “ancient”) networking products for SNA and even pre-SNA network topologies. Their withdrawal should not be a surprise. These products were used in conjunction with the IBM 3745 and 3746 Communications Controllers and their predecessors. “No replacement.” No, there really are replacements. The most common replacement is probably Enterprise Extender (EE), a feature within Communications Server for z/OS, a no additional charge, base component of the z/OS operating system. IBM published a helpful migration guide about 7 years ago, and Chapter 19 discusses EE. Oddly enough, none of the co-requisite products that ACF/NCP and ACF/SSP support (IBM 3745, IBM 3746, IBM Communications Controller for Linux) are still supported. (CCL was the last remaining holdout, but standard support for that product ended on March 31, 2016.) That’s probably why the end of standard service date for ACF/NCP and ACF/SSP is August 31, 2016. If I had to guess, it looks like somebody at IBM forgot to withdraw support for ACF/NCP and ACF/SSP at the same time support ended for CCL. Well, now that’s fixed.

Anyway, don’t panic if you see “No replacement” in an IBM product withdrawal announcement. Simply discuss your migration and upgrade options with “your friendly IBM representative,” and strike a mutually agreeable deal (technical and financial). There are almost always excellent replacement options, often plural, even if IBM doesn’t initially, explicitly tell you what they are in the official product withdrawal announcements.

The Watson Dynasty:  10th anniversary on a IBM Historical Account


I read The Watson Dynasty, by Richard S. Tedlow back in 2003 when it was first published.   Ten years later I’m re-reading this IBM Classic account and re-introducing myself to the mindset and philosophies of IBM’s founding father and son, T.J. Watson Sr. and T.J. Watson Jr.

The book is interesting from the point of view of adventures in business and rags to riches empire building.  While the book certainly talks about and touches on the great innovations and technology that IBM created, the purpose of the book is to account the history of how IBM grew into the powerhouse its knows for by the Watson father and son leadership.

Thomas J. Watson Senior

Starting with Thomas J. Watson Senior’s life and character you get a sense right off the introduction that this is not your typical business leader.  The opening example of taking what would be a crippling train accident with hundreds of his employees during IBM Day at the second New York World’s Fair in 1940, and turning it into an flourishing opportunity.

I found T.J. Watson’s life a fascinating and relentless battle.   Here’s an excerpt at age twenty-one:

‘The only place for him to rest his head at night was a pile of sponges in the basement of a store.  Watson went from rags to riches, but he did not begin life in rags.  He worked his way down before he worked his way up.’

What’s interesting is learning how at the roots of IBM’s history was computation devices such as scales and cash registers.  It was through a series of lucky opportunities and hard work and love of selling that allowed T.J. Watson  Sr. at the beginning of his career to found International Business Machines and turn it into a market leader.  In fact he was so successful and so cut throat to the competition he was faced under devastating anti-trust lawsuit in a former company he headed the sales with before founding IBM.

T.J. Watson Sr. is also certainly known for his famous quote,

“Would you like me to give you a formula for… success? It’s quite simple, really. Double your rate of failure.”

This philosophy is captured by Tedlow as he touches on some other gems I found interesting about Senior.

‘Senior was a big tipper…His son asked why.

     “I do this for two reason, Tom.  First, that fellow…I feel sorry for him.  The second reason is that there is a whole class of people in the world who are in position to poor-mouth you unless you are sensitive to  them…They see you in an intimate fashion and can really knock off your reputation.”

Junior (aka “Terrible Tommy Watson”)

After  getting a sense of T.J Watson Sr. as the “Man of Men”, the book begins to account the life and character of Junior.  Described by college presidents and administration people as a “predetermined failure”.  It’s difficult not to feel sorry for “Terrible Tommy” overshadowed by his father’s legacy and depending on his father’s influence to get him into Brown University.

The bickering between father and son only intensifies as Junior followed in his father’s footsteps working and leading IBM on.

“Terrible Tommy failed at most of the things he tired.”

It interesting to see how “Terrible Tommy” despite other people’s expectations and the battles between him and his father how he later saves IBM from “The Old Man” as the dawn of electronic computers arrived and later the pushing force behind mainframes.

Intangible vs. The Punch Card in Hand

It’s half way in the book, Chapter 17, before electronic computers are introduced.  Before that IBM was running a sophisticated business with sophisticated technology running gears to compute and calculate  the numbers for businesses.  This way of doing the job obviously takes a drastic change once World War II introduced a “computer revolution”.

The Electronic Numerical Integrator and Computer (or ENIAC) project, funded by the Army Ballistic Research Laboratory  at the University of Pennsylvania’s Moore School of Engineering, proved to out perform IBM’s fastest punch card machines in 5000 additions per second to 4!

While ENIAC at the time was acres of vacuum tubes that attracted moths (hence the term “debugging”) the “electronic brain” was born!

It’s interesting obviously in hindsight as the first computers were being engineered and IBM trying to convince customers the validity and utility of this new technology.  Senior had the customer’s interest in mind with having a tangible IBM punch card with the information that could be held in the hand, while Junior represented the new generation and influence where information was moving on to magnetic tapes becoming an intangible solution to storage woes of some of IBM’s biggest customers.  One of the them described they had 3 floors of typists on punch cards.


The true arch in the story, and what will interest many Millennial Mainframers, is the intense gamble IBM took creating System/360.  It was without a doubt a HUGE undertaking.  Tedlow quite boldly states:

‘The System/360 was one of the two greatest new product introductions in the twentieth-century American business history.  The other was the Model T Ford.’

It goes into detail explaining how System/360 took $5 billion over a period of four years and close to 2000 programmers.  The name 360 was in reference to all points of the compass.

Internal conflict and shaky belief that System/360 would ever succeed threatened the entire project as it slowly progressed forward.   When it was finally revealed the earliest customers were Bank of America and NASA proving to be a compelling and superior product that it brought about another antitrust lawsuit against IBM.


I liked the book.  Although be warned its a historical account of IBM and the Watson Dynasty, thus the hardcore nerdy technological details are missing and broadly covered.  Tedlow however does a fantastic job covering the historic business of IBM.

Probably the most interesting aspects of this book is that despite IBM being a huge empire making big moves and influencing the business world, at the center of it all was some family drama.

My favorite part obviously is the struggle and calculated risk IBM took pushing System/360 into the world.  System/360 was the predecessor of the now famous z/OS mainframe operating system still used extensively today.

I recommend checking this book out!

(Read more about The Watson Dynasty here:  The Watsons: IBM’s Troubled Legacy )

*** full disclosure: some of the Amazon links have affiliate links to support Sean McBride’s efforts with MillennialMainframer.com ***