I'll agree with Alan on this  You'll need:

1.      Some kind of ESM such as RACF, VM:Secure, ACF/2, Top Secret, etc.

2.      Some kind of directory manager such as DIRMAINT, VM:Secure,
VM:Direct, etc.
3.      Some kind of performance monitoring tool, such as RTM, PRF, FCON,
etc
also:
4.      If you want to recover or track costs for CPU, DASD and Tape usage,
some kind of account handling software, such as VM:Account
5.      Software for backing up Linux.  DDR (comes with VM) will do it but
only on a server-as-a-whole basis.  File-level backups need something like
Tivoli TSM or CA Brightstar.  There are several other programs due to go GA
within a couple of months.  You can also do it from within Linux using
Amanda or other similar programs.  Either way, you'll want some type of tape
handler like VM:Tape
6.      If you'll be using linux for e-mail or as a Samba server, you might
look into software that will scan e-mail inboxes and samba shares for
viruses.  There is (I'm told - I can't give any specifics off the top of my
head) open source software for doing this and several  commercial products
about to hit the market within a couple of months.

There's a lot of infrastructure that you'll have to write yourself.  How to
clone Linux images. (Investigate VMLinMan and STK's SnapVantage)  How to
route console messages to PROP or VM:Operator.  How to use AUTOLOG to start
(and stop?) Linux images.  How to use RSCS as a LPR/LPD print handler.   How
to set up TCPIP for multiple Linux images so you don't have to take it down
every time you want to add another image.  How are you going to route fixes
around to dozens of Linux images?
Most of this can easily be written in REXX.  I've only had to write one
accounting exit in assembler for our special accouting needs.

A good source for all of this is SHARE (San Francisco, August 19-23).  IBM
has several redbooks on implementing Linux on the mainframe.  Also, check
the archives of this list and Mark Post's page at www.linuxvm.org

Good Luck!

"You do not need a parachute to skydive.  You only need a parachute to
skydive twice."  -Motto of the Darwin Society
Gordon W. Wolfe, Ph.D.  (425) 865-5940
VM Technical Services, The Boeing Company


> ----------
> From:         Alan Altmark
> Reply To:     Linux on 390 Port
> Sent:         Tuesday, June 4, 2002 10:54 AM
> To:   [EMAIL PROTECTED]
> Subject:      Re: What's needed with z/VM?
>
> On Tuesday, 06/04/2002 at 11:32 AST, "Kittendorf, Craig"
> <[EMAIL PROTECTED]> wrote:
> > We're currently have SuSE Linux/390 in an LPAR. Management is asking
> about
> > z/VM and I really know very little about it.
> >
> > If we get z/VM to run Linux/390 as guests, what else would be required
> (not
> > just desirable)  beyond the base z/VM, e.g. RACF or Top Secret, etc?
>
> Well, nothing else is "required", but it is highly recommended that you
> get
> - an external security manager such as IBM's RACF.  In addition to
> simplifying security administration, it makes passing system security
> audits much easier.
> - a directory management program such as IBM's DirMaint.  Reduce the time
> it takes to deploy virtual servers and elminate costly human errors.
> - a performance management suite such as IBM's FCON, Real-Time Monitor,
> and/or Performance Reporting Facility.  It's the only effective way to
> monitor and tune system performance.  While it can be done "by the seat of
> your pants", I don't recommend it.
>
> In all three cases, there are non-IBM solutions available from other
> vendors.
>
> Alan Altmark
> Sr. Software Engineer
> IBM z/VM Development
>
>

Reply via email to