The following message is a courtesy copy of an article that has been posted to bit.listserv.ibm-main as well.
[EMAIL PROTECTED] (Anthony Saul Babonas) writes: > Please colleagues, allow my to clarify by stating : > > SET FAVORITEEXPLETIVE='' > > 1. I do not believe "other platforms" are &favoriteexpletive. > 2. I am not arrogant and certainly not blind. > 3. I am not responsible for the mainframe market share situation. I neither > buy nor sell mainframes. > 4. I have heard the costs of hardware and software, but I still believe > arrogance is no cost. > 5. I do understand the competition (&favoriteexpletive). > 6. Recent young graduates are free to work on any platform of their > choosing. Undoubtedly the market influences > their choices. > 7. I do believe the learning curve for Novell, circa 1995, was orders of > magnitude less than zOS + subsystems, circa 1995. > > So fast forward 12 years, "is learning to be a PC based network "sysprog" > more difficult than zOS, less so, or about the same? > > Please note, final question is posed without beliefs, opinions, standpoints, > political biases, or prejudices. I reserve the right to invoke arrogance at > some later date. a little x-over http://www.garlic.com/~lynn/2007j.html#47 IBM Unionization http://www.garlic.com/~lynn/2007j.html#48 IBM Unionization from afc ng thread ... w/regard to post references some national labs ... discontinuing mainframe systems in the 90s because of inability to fill positions for system support (schools were turning out lots of unix skills but little or no mainframe skills). It wasn't a particular cost issue, it was an issue about being able to find/hire the skills. part of the problem is getting into a negative feedback loop ... programs to turn out mainframe skills can take a decade ... once it starts the reputation about skill shortages can contribute to choices made about platforms to use ... and the choice about platforms to use can contribute to choices about skills required. for totally other topic drift ... in the very early 80s, the disk division had a PC network server project ... part of the implementation was being done under a work for hire contract by people in Provo. For a while, one of the people on the project was commuting between San Jose and Provo nearly every week. At some point, the corporation decided to cancel the project ... and allowed the group in Provo to retain rights to the work they had already been paid for. Not long afterwards there appeared a PC network server company out of Provo. misc. past posts mentioning DataHub project: http://www.garlic.com/~lynn/96.html#4a John Hartmann's Birthday Party http://www.garlic.com/~lynn/2000g.html#40 No more innovation? Get serious http://www.garlic.com/~lynn/2002f.html#19 When will IBM buy Sun? http://www.garlic.com/~lynn/2002g.html#79 Coulda, Woulda, Shoudda moments? http://www.garlic.com/~lynn/2002o.html#33 Over-the-shoulder effect http://www.garlic.com/~lynn/2003e.html#26 MP cost effectiveness http://www.garlic.com/~lynn/2003f.html#13 Alpha performance, why? http://www.garlic.com/~lynn/2004f.html#16 Infiniband - practicalities for small clusters http://www.garlic.com/~lynn/2005p.html#23 What ever happened to Tandem and NonStop OS ? http://www.garlic.com/~lynn/2005q.html#9 What ever happened to Tandem and NonStop OS ? http://www.garlic.com/~lynn/2005q.html#36 Intel strikes back with a parallel x86 design http://www.garlic.com/~lynn/2006l.html#39 Token-ring vs Ethernet - 10 years later http://www.garlic.com/~lynn/2006y.html#31 "The Elements of Programming Style" http://www.garlic.com/~lynn/2007f.html#17 Is computer history taught now? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
