Just define your Linux LPAR as you would a z/OS LPAR. The CP type
'LINUX' refers to an IFL engine (Integrated Facility for Linux), which
from your description you do not have. Yes, all LPARS assigned to a CP
must be the same type.

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Rakoczy, Dave
Sent: July 31, 2007 08:14
To: LINUX-390@VM.MARIST.EDU
Subject: Defining an LPAR on a z box to run LINUX

We are researching the possibility of putting up a LINUX LPAR on our
z/890 for a Proof of Concept.  We currently have 3 general purpose CP's
turned on in the box. 
All 3 of the general purpose CP's are available for use to the 3 z/OS
LPAR's we run on the machine, none of the CP's are dedicated.  I know on
the HMC's Activation Profile you can select the LPAR mode ESA/390 or
LINUX (and a few other options as well).  

What I'd like to do is Build a 4th LPAR to be a LINUX LPAR, assign that
LPAR just a single processor, it's own Devices via IOCP along with a
chunk of memory.  This LPAR would just be for me to play around with and
learn on.  Now my question is the following.  Since all three of my
General Purpose CP's are shared across LPAR's that are EAS/390 Mode
LPARS, can I use one of those same three General Purpose CP's for this
LINUX Mode LPAR?  Or must all LPAR's assigned to a CP be defined as the
same mode type?  i.e.  EAS/390 or LINUX.

-Thanks
Dave.    

----------------------------------------------------------------------
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


The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material.  Any 
review retransmission dissemination or other use of or taking of any action in 
reliance upon this information by persons or entities other than the intended 
recipient or delegate is strictly prohibited.  If you received this in error 
please contact the sender and delete the material from any computer.  The 
integrity and security of this message cannot by guaranteed on the Internet.  
The Sender accepts no liability for the content of this e-mail or for the 
consequences of any actions taken on basis of the information provided.  The 
recipient should check this e-mail and any attachments for the presence of 
viruses.  The sender accepts no liability for any damage caused by any virus 
transmitted by this e-mail.  This disclaimer is the property of the TTC and 
must not be altered or circumvented in any manner.

----------------------------------------------------------------------
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

Reply via email to