Not clear what you are asking. The only applicable restrictions for z/os.e are:
1. No COBOL complies. 2. COBOL programs must run under the CEEPIPI interface (documented in the LE manuals and the T&C for z/os.e). 3. TSO USERMAX of 8. Using z/os.e to manage data replication and as a 'floor' system sounds like a perfect fit. Actually, we run all of our production under z/os.e except for TSO. We don't do COBOL compiles at all (a vendor supplies all of our COBOL code). Local programs are written in C. A combination of z/os.e and sub capacity pricing is taking a *serious* bite out of our software bill. What 'sprit' are you concerned about? -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John (IBM-MAIN) Sent: Wednesday, February 22, 2006 2:40 AM To: [email protected] Subject: Re: Backup of Offline Data (at a remote site) -- snip -- Run z/os.e on a very small CPU with upgrade on demand at your BR site. The backup steps don't need a lot of CPU power, and z/os.e is cheap. Very cheap. Once you pull your DR trigger, upgrade the box and start recovering your LPARS. The z/os.e LPAR can remain active to assist as a 'floor' system. -- snip -- Interesting. I'm assuming that one could set up a z/OS.e system(s) running XRC to take care of mirroring the secondary data. Is this in the 'spirit' of z/OS.e? John ---------------------------------------------------------------------- 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
