If the person is interacting ONLY with the Linux portion, you need to learn a few things about the mainframe but not a lot -- you could compare the problem to learning/understanding a new BIOS. The stuff inside the Linux guest is the same as on other platforms.
If the person is responsible for the entire environment (virtualization, automation, etc), then mainframe expertise (and specifically, z/VM) is more important. Most organizations treat that as the logical dividing line -- existing mainframe people manage the container (z/VM, hardware, etc), and the Linux folks manage what goes into the container. Don't forget to incorporate some networking folks into the team, too. > -----Original Message----- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of > Mark Smith > If running Linux on an IBM mainframe, do you need to have a "mainframe" > expert to administer the system or is a Linux expert sufficient? ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/