I know it's risky. RACF copies just fine. Catalogs are OK. We currently assume it will be a one way operation. Once the catalog is used on z/OS 1.7 it will be unusable on OS/390. We will use OFFLOAD to copy the JES SPOOL. Probably also a one way operation. We do not use HSM or RMM.
Gadi -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of R.S. Sent: Wednesday, July 26, 2006 1:19 PM To: [email protected] Subject: Re: Upgrading from OS/390 v2.10 to z/OS 1.7 גדי בן אבי wrote: > Hi, > > We are in the final stages of our upgrade project. > > The powers that be want to know if anyone has performed such an upgrade? > Were there any significant problems? > > Are there any known bug is z/OS 1.7 that we should look out for? > > Our current environment is: > Two z890's. Each has a production LPAR and a system test LPAR. The production > LPAR's are connected in a basic SYSPLEX using CTC's. > > Software running is OS/390 v2.10, CICS TS 1.3, ADABAS and NATURAL. It is unsupported upgrade, so you have to pay special attention to operational datasets upgrade/conversion/use. I mean RACF db, ICF BCSes, HSM, RMM CDSes, JES spool and checkpoint, etc. etc. Theoretically you could re-create them from scratch, but in real world you would want to use existing ones. It can be risky. -- Radoslaw Skorupka Lodz, Poland ---------------------------------------------------------------------- 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
