I agree with Alan - the list is much broader.. I've updated below what I've seen my customers using, using Alan's list. Not sure if this is what you want, Michael - but FWIW:
Scott On Mon, Jul 7, 2008 at 2:30 PM, Alan Altmark <[EMAIL PROTECTED]> wrote: > On Monday, 07/07/2008 at 04:08 EDT, Michael > MacIsaac/Poughkeepsie/[EMAIL PROTECTED] wrote: > > > Define "systems management" :) > > > > Yes, that is what I hope to do in an hour at SHARE :)) > > > > I tried to leave the "form" open-ended. But let's say systems management > = > > monitoring, provisioning and patching, while performance management is > > perhaps a separate science unto itself. > > In preparing some z/VM course material, I found myself having to define > "z/VM system management". It turns out that you have: > - Provisioning (real and virtual) Typically inhouse scripting - with RH Linux - using kickstart. DIRMAINT or VMDIRECT (CA) or manual directory edit for provisioning > > - Human operations (IPL, shutdown, health inquiry, dump processing, ...) inhouse scripting > > - Automated operations PROP, inhouse scripting > > - Security (authentication, authorization, audit) Directory (no ESM), RACF, ACF2, VMSECURE (CA) > > - Performance monitoring and management PTK, Velocity, Omegamon (green screen and XE) > > - Backup/Archive TSM for Linux guests, VTAPE, Flashcopy SE, in house scripts > > - Disaster planning and recovery Lots of data mirroring going on - PPRC, XRC, etc - various solutions > > - Availability management (probably tied with disaster planning) Nagios (groundworks), Omegamon, Prognosis > > - Problem determination and Service (patching) Inhouse scripting (usually revolving around ssh) , Aduva > > - Software and configuration change control > > Some require more in-depth knowledge than others, but all are required to > have an industrial-grade system. If you ignore one or more areas, then > you will waste time or money (usually both). > > Alan Altmark > z/VM Development > IBM Endicott > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
