OK, here are my definition:
SYSADMIN: A good SysAdmin will look up a message in the Systems Messages and Codes manual. Upon seeing: "Response: Contact your Systems Programmer", has someone more skilled to call upon.
SYSPROG: A Systems Programmer will usually not look up a message in Systems Messages and Codes until all else fails. When finally reading: "Response: Contact your Systems Programmer", will exhale loudly, maybe mutter an expletive or two about **BEING** the SysProg (and in Adam's case: open a case of cough medicine). A **GOOD** Systems Programmer will then consult the source code, and finally, if unable to resolve the problem -- gather complete documentation and submit the doc with the first report to IBM or an ISV when opening the problem report.
Mike Walter
Hewitt Associates
The opinions expressed herein are my own, not those of my employer.
| "Alan Altmark"
<[EMAIL PROTECTED]>
Sent by: "VM/ESA and z/VM Discussions" <[email protected]> 01/10/2006 12:20 PM
|
|
On Tuesday, 01/10/2006 at 09:48 PST, "Schuh, Richard" <[EMAIL PROTECTED]>
wrote:
> I do not know of too many shops who do not handle the distinction by
giving one
> person two hats. What is a sysadmin? Answer - A system programmer who
also
> handles the bulk of the administration of the system. What is a system
> programmer? Answer - A system administrator who handles the tasks of
system
> programming. I have never worked in a shop that separated the two
functions. If
> it was anything more that creating a new userid (using tools created by
the
> system programmer) or resetting a password, it was the prevue of the
system
> programmer/administrator.
I agree that in many (majority?) of today's systems there is the sysprog
and then there's "everyone else". But it is my perception that larger
companies seem to be trying to reestablish the once-common "middle class"
of sysadmin. That is, the people who are charged with the day-to-day
management of the system, but who will "contact their system support
personnel" when things go wrong. I think this is likely a salary issue:
Pay more for sysprogs, less for sysadmins. They want to grow, but not
hire more sysprogs just to handle the routine tasks of system management.
(I'm not particularly interested in drawing the line between the two; it's
fuzzy at best, and it's a decision best left to you, the customer.)
Alan Altmark
z/VM Development
IBM Endicott
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
