VM/370 security and performance ALSO MAILERS

[lcc.barry at UCLA-LOCUS.ARPA]

Sorry for posting this to unix-wizards, but some mailer between Dick Dunn and
here is broken and records his return address as "rcd at opus.uucp" which is
not a reasonable address unless you happen to be adjacent to rcd (I'm not).

I hope someday somebody can negotiate a truce between Rich Wales' (UCLA's)
postman and UCB's sendmail.

===============================================================================

I'm replying directly to you.  This discussion no longer belongs in
unix-wizards.

>>With VM, you do your work during the day...(then) come in ONE night... (me)

>True enough for systems which run UNDER VM.  However, as barry pointed
>out later in the same article, the once-simple VM has grown an unfortunate
>number of features and enhancements.  SO, this means that you get to
>come in between 2 and 6 AM to work on VM. (Dick Dunn)

Even though VM has grown an alarming number of features, you can STILL run it
in a virtual machine.  (Err, *crawl* it in a virtual machine).  I used to do
that all the time when testing KVM/370, and I did it when upgrading from SP2
to SP3.

I don't usually bother for minor enhancements like changing the configuration
(DMKRIO).  I just wait till most people are at lunch, tell the rest to take
a 5 minute break, shutdown, and IPL.

There will still be some cases where you have to work at night, of course.
If you have a fancy network or other special device that your production depends
on and it's not virtualizable and you only have ONE, well that's the way
it goes.

barry