It's capitalism at its -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ivan Warren Sent: Saturday, November 14, 2009 12:41 PM To: [email protected] Subject: Re: IBM driving mainframe systems programmers into the ground
Paul Gilmartin wrote: > On Fri, 13 Nov 2009 14:15:57 -0800, Howard Rifkind wrote: >> In fact I believe there really is a very good chance to see the need for sysprogs disappear completely. Log into an IBM web site and download all the updates, fixes, new operating systems etc. >> > And, taking an unbiased view, this would be bad > because ... what? > > -- gil > > ---------------------------------------------------------------------- > 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 Let me tell you *I* personally think this is bad ! Anyone (and I mean - really pretty much *anyone*) can do the basics on any modern system : Install the system, maintain it up to date, upgrade to the next release, etc.. That's true for Windows, Linux, AIX and to a lesser extent today for IBM i, z/OS or z/VM.. For the 'distributed' OSes (the 1st category), anyone can acquire the skill set to do that in probably a couple of weeks of training (and IMHO, AIX is the easiest !). For the 2nd category, this may take a little while longer, but it's still accessible (maybe a couple month or so..). But being a "Systems Programmer", "Systems Administrator" or however you call it is not *just* that ! That's really the tip of the proverbial iceberg. There are, to me, 2 more essential functions that are provided by this category of personnel : 1st, you have the task to adjust the system environment to the actual business need of the company. This will pretty much depend on several factors, such as the type/brand/make of business software installed, the requirements (and each being utterly different) of these applications. Efforts are definitely being done in that field through stuff like ITIL and ISO 20000 - Standards and recommendations that are making an effort to standardize systems requirements in regard to the actual business requirements. 2nd, you have the task to answer to whatever demand is made by the company's Executive management staff. Ah! That one is really not so clear cut. Here you have, with a mismatched assembly of people, some with different goals and tactics - And remember - the actual CIO is usually part of that team ! And in most cases, this management position entails 2 contradictory requirements : lower costs while at the same time ensure that both the 1st item is met while also ensuring business continuity and diminishing the risk factor. And *THAT* very second item is where an experimented "sysprog" comes into play. Until someone develops an AI process that is capable of reconciliating all the contradictory requirements of item #2, the qualified, competend and experienced in-house (with understanding of a company's philosophy) sysprogs are still the cheapest and most efficient way for an IT department to manage a company's information technology system. --Ivan ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
