I'm being nitpicky. z/VM runs very well on an IFL.
Tom Duerbusch THD Consulting (just addding in another penny) >>> LOREN CHARNLEY <[EMAIL PROTECTED]> 7/6/2007 3:54 PM >>> If you are trying to run an OS other than LINUX on an IFL, you will not be successful, OS390 / zOS, etc. must be run on a standard processor. If running on a ZFrame, you can only run in 31 bit mode. I don't know anything about OS390 or zOS in particular but from the posts that I have read so far, it looks like a hardware problem and you will need to find a fix somewhere. Just my .02 worth...... Loren Charnley, Jr. IT Systems Engineer Family Dollar Stores, Inc. (704) 847-6961 Ext. 7043 (704) 708-7043 [EMAIL PROTECTED] -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Friday, July 06, 2007 2:37 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: OS/390 as zVM 5.2 Guest on z9 ?? > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard > Sent: Friday, July 06, 2007 1:14 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: OS/390 as zVM 5.2 Guest on z9 ?? > > > I would venture a bet that the error when trying to IPL an unsupported > operating system in an IFL has never depended on something > buried in the > operating system's ipl code. It is not that the O/S is IFL > aware. Quite > the opposite, that the IFL is O/S aware, is the only way to > enforce the > restriction with any assurance that it is being enforced. If it were > buried in the ipl code of the O/S, it would be subject to > being cracked, > probably with only minimal effort. > > Regards, > Richard Schuh You could well be correct. Unless the code is a DIAG that must execute correctly to set up something that z/OS needs in order to run. And said DIAG on an IFL causes the "machine check" when executed on an IFL. However, you are correct that I don't know. I do know, from reports, that z/OS runs on Hercules/390. So Hercules implements the "whatever" that z/OS needs. But I've never looked deeply enough in the Hercules source code to see what that is. But I doubt that Hercules implements the "let's see if it is z/OS and hard wait if so", which is what can happen if Hercules/390 is not set up to run z/OS with a runtime parameter. -- 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. ----------------------------------------- ************************************************************ NOTE: This e-mail message contains PRIVILEGED and CONFIDENTIAL information and is intended only for the use of the specific individual or individuals to which it is addressed. If you are not an intended recipient of this e-mail, you are hereby notified that any unauthorized use, dissemination or copying of this e-mail or the information contained herein or attached hereto is strictly prohibited. If you receive this e-mail in error, notify the person named above by reply e-mail and please delete it. Thank you.
