Re: Beta Production LPAR(s) setup.
Hi, I just finished two more conversions (at two separate sites) to z/OS from OS/390 V2.6 and V2.9, one went to Z/OS.e and the other to Z/OS (one was a university that didn't need to run CICS and had VERY little COBOL, so the cost of z/OS.e was just too good to pass up). Both went from older 9xxx based hardware to z/series boxes (one was a z/800, the other was a z/990). Both conversions took a lot of planning, more because of the age of the exits they had, (especially the JES2 ones) and the fact that many of their old procedures were no longer necessary. There were some hardware issues, since the newer z/series boxes both had only ESCON and FICON cards, so the old Parallel hardware had to be replaced or dropped mostly (at one site we bought an Optica converter which worked perfectly for them). If you would like to discuss the how-to's and what to look out for, then we should do it off-line form this list because I don't want to bore everyone. Send me an Email and I'll give you my contact information. In a nutshell though, if you have the DASD space to have 3 LPARs, (your old OS/390, a test and a production z/OS) you will be good to go. The 3 will only co-exist for a VERY short time. The test will eventually become your production LPAR, and you will then need a new test LPAR, so you can get by with just 2 defined, but you have more fallback opportunities if you can keep all 3 for the critical conversion time, (which will probably be a week or two at most). Brian -- 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
Beta Production LPAR(s) setup.
Dear Colleagues, We have a new Z/os capable machine we will be moving our current work load onto. We have a LOT of disk space on SHARK. We are primarily CICS/DB2/COBOL with some CICS/VSAM COBOL. We are not at modern levels of the OS or CICS currently. We have not exploited to any extent CICS/TS web capabilities. We are on DB2 version 7. Most of our CICS is non-TS. Our plan is to create an LPAR and move our current OS/390 production environment to that (my understanding this is possible with the proper patches in place). Then create a second LPAR that can be refreshed in a timely (daily) manner to either match the current environment or be IPL'ed into a Z/os environment for migration testing etc. We use RACF and SMS. We could even think about having three, one with the production environment, one with a clone of the production environment, and one that stays at Z/os for on-going migration and testing. I have been at one shop that set up a full copy BETA LPAR for Y2k and then kept it since it was VERY useful for both system and application testing. Each morning, the two LPARS start out identical unless a group has asked for the BETA LPAR to be IPL'ed in a different fashion. It can be reserved by systems programming or various application areas for private use in advance. I have some general questions. 1. Have you done this or thought seriously about it? 2. What were the top three gotchas you discovered along the way to putting this type of cloned production environment together? One I know about is to disabled certain automatic or scheduled activities. Another is to disallow or control FTP processing to the Beta LPAR is my assumption. 3. Do you have any overview document you could share that outlines how yours is set up, what additional software (flashcopy, other?) or hardware you needed. 4. I figure the licensing in this situation is a bit bizarre, but at this point, I am interested in the configurations people have used to accomplish this type of environment. Thanks in advance! Kriss - (Mr.) Kriss Davis, CCP Illinois State University [EMAIL PROTECTED] 309-438-2802 - -- 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
