We do it here off of one res volume. We currently run Z/os and Z/os.e in a non parallel sysplex mode. We do have different HFS files for both and then there are also different parmlib members. You also have to set up GRS, but other than what's been mentioned it's pretty easy.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John Eells Sent: Wednesday, August 31, 2005 7:35 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: z/OS and z/OS.e maintenance/licencing [EMAIL PROTECTED] wrote: > Cross posted to LPAR-Pricing, ISVCosts and IBM-Main lists > > As I understand it licencing z/OS.e works out significantly cheaper than > z/OS, however in a traditional z/OS shop that is looking to bring in new > workloads the trade off is that you have to maintain multiple builds - one > for z/OS and one for z/OS.e. > > What are people thoughts about providing the option in z/OS to IPL it as > z/OS.e - enabling a single sourced build to be used for both purposes? <chop> What you propose exists today. You do *not* need to do two system builds to run both z/OS and z/OS.e. (In fact, this was a z/OS.e design objective.) They are binary images of one another, differing only in hardware support (you need a z890 or z800), parmlib setup, LPAR naming, and licensing terms. You can even share the SYSRES! For more detail, see z/OS and z/OS.e Planning for Installation. -- John Eells z/OS Technical Marketing IBM Poughkeepsie [EMAIL PROTECTED] ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
