> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of John S. Giltner, Jr. > Sent: Thursday, March 13, 2008 10:07 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: z/OS and Linux on same z/VM Image > > > Dinesh wrote: > > Hi, > > Is it possible to have both z/OS and Linux on same > z/VM? If so > > which volume type I have to use (either FB or CKD). In some IBM > > manuals they mentioned that both IFL and CP cannot be shared for a > > Lpar. > > > > > > Thanks & Regards, > > Dinesh. > > A single LPAR can't have a IFL and a CP.
The new z10 can do this now. It is specifically designed so that a single instance of z/VM can run in an LPAR, dispatching z/OS (et al.) on a CP while dispatching z/Linux on the IFLs. > > However you can run z/VM in a LPAR using CP's only and you > can run both > z/OS and Linux under that z/VM. True, but expensive since the CPs running z/VM and z/Linux still cause the z/OS software prices to go up (in many cases). > > Linux will run under both CP's and IFL's, both on bare metal > or under z/VM. True. But z/Linux under z/VM is usually considered to be "better". -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
