Even with the multi-programming capability of linux, I might prefer to separate some functions. I think things like DIRMAINT, PERFTK, VMUTIL, SYSLOG, other internal functions being in one server, RSCS, VTAM/SNA(if necessary), TN3270, FTP, NFS, Web, other external functions being in another server, and user accounts in another. I would feel more comfortable consolidating into a couple of servers before consolidating everything into a single server.
I would definitely like to work on moving VMUTIL, PERFTK, and SYSLOG functions into a properly stripped down linux server. /Tom Kern /301-903-2211 Mark Post wrote:
Heavy, being somewhat relative. Before the use of OSA interfaces (virtual or real) and the huge increase in
"required" rpm packages I was routinely running SLES systems in about 32M of virtual storage. Given the assumption that you would only need one Linux versus several CMS VMs, it's fairly easy to buy back the virtual storage. CPU usage, perhaps not so easy, but not so bad either. And then, you would probably want to have two Linux systems up and running in an active-active cluster to avoid a single point of failure.
As MacK pointed out, rearchitecting and recoding all the infrastructure products that currently run on CMS would be a huge undertaking for a lot of companies. Not likely in our (professional) lifetime. Still, it would be nice to have things like RSCS, DIRMAINT, etc. all running in the same VM, as opposed to being spread all over the place. I just wouldn't want to be the one in charge of even the IBM piece of such a project. Mark Post
---------------------------------------------------------------------- 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
