CPC replacement
Dear listers, We are *replacing* our Z890 CPU by Z9 BC. Z9 BC does not cick in unless we power off Z890. I would appreciate if you can guide me or provide me pointers in the right direction: a) We are moving our OSA cards and have downloaded OSA configurations using OSA/SF and plan it to upload on OSA using new CPU. will it work.. any concerns? b) How can i include new processors in the HMC GROUP. c) as we are moving all cables from old CPU to NEW CPU- we are migrating our HMC web server / OSA Integrated console configuration. will that work. We have checked PSP buckets and all fixes have been applied. Is there any other gottcha's we need to be concerned. regards, Munif -- 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
Re: CPC replacement
All the work Tom is doing involves having both machines running beside each other. It appears you are doing what is called a Pull-Push operation. Everything Tom mentioned can be applicable to your upgrade. As far as defining the new processor, you could start with HCD, and use the ADD LIKE option when you select the processor option. At that point you can change the needed information, then continue to edit and change the CHPID information to match the new machine configuration. Have you gone through a Systems Assurance meeting with IBM's CEs, Sales, etc? All this is usually discussed and noted during the meeting, along with a detailed document passed around which goes over all the steps involved in the machine upgrade. On Fri, 12 Oct 2007 08:01:08 -0400, Chicklon, Tom [EMAIL PROTECTED] wrote: Munif, if all goes according to plan, we will be moving our production z/OS system from our z/890 to a new z9 BC tomorrow. We moved our sysprog sand box over a couple of days ago. We are *replacing* our Z890 CPU by Z9 BC. Z9 BC does not cick in unless we power off Z890. I would appreciate if you can guide me or provide me pointers in the right direction: a) We are moving our OSA cards and have downloaded OSA configurations using OSA/SF and plan it to upload on OSA using new CPU. will it work.. any concerns? Not sure what you mean by moving your cards, are you physically moving the cards, or just moving your IP network to new cards on the z9? We have new ones on the z9, and thus just moved the IP connectivity to the z9. I was stressed about how to do this as well, all for nothing, it's just that I had never had to configure or load OSA cards before. OSA ignorance on my part I guess. The cards seem to get configured just fine when VTAM and TCP come up. We didn't have to manually load or configure anything with them, other than to make minor changes to VTAM and TCP parms because the physical address on the cards changed with the z9 (different PCHPID) and we happen to use this as part of the names for the cards in VTAM and TCP. One other thing we did was to make the cards 1000M instead of 100M as our local network was just upgraded to support gigabit. We was a simple change on the HMC (we don't trust auto negotiate, the default for the cards when the box was shipped to us). Not at all related to the new z9, just a good time to make this change here. b) How can i include new processors in the HMC GROUP. We're finding this process to be about as clear as mud. Three years ago when our z/890 was installed, the CE copied these definitions over from the last CPU. So the last time anyone here messed with setting these up was about 7 years ago. The CE didn't copy these over this time. We've still not gotten this set up the way we want, but are getting there. I'm sure we could copy them over, but this is a good time to start over from scratch and maybe set things up a bit differently. c) as we are moving all cables from old CPU to NEW CPU- we are migrating our HMC web server / OSA Integrated console configuration. will that work. I don't see any reason why this won't work. We've moved over the cables used by our test system to the z9 so far, channels dedicated to our production system get moved over tomorrow. We have checked PSP buckets and all fixes have been applied. Is there any other gottcha's we need to be concerned. I had checked PSP a two weeks ago, and found I was all set. Last week, I pulled current PSP buckets and found that two new PTFs were called for. So don't overlook pulling them again as you get closer to cutting over. The only other 'gotcha' so far was with a channel that had an ESCON converter on it with bus and tag cables to a 3174 and 3490 tape drives. When we moved this channel over, the converter's error light came on and the channel didn't come on line to the z9. Power cycling the converter didn't clear the problem, but what did work was to power off the converter, then IML the 3174, then power the converter back on. We have 4 more channels with converters on them to move tomorrow, so we'll have to wait and see how that goes. Feel free to contact me Monday to see how this weekend goes. Tom Chicklon -- 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
Re: CPC replacement
Munif, if all goes according to plan, we will be moving our production z/OS system from our z/890 to a new z9 BC tomorrow. We moved our sysprog sand box over a couple of days ago. We are *replacing* our Z890 CPU by Z9 BC. Z9 BC does not cick in unless we power off Z890. I would appreciate if you can guide me or provide me pointers in the right direction: a) We are moving our OSA cards and have downloaded OSA configurations using OSA/SF and plan it to upload on OSA using new CPU. will it work.. any concerns? Not sure what you mean by moving your cards, are you physically moving the cards, or just moving your IP network to new cards on the z9? We have new ones on the z9, and thus just moved the IP connectivity to the z9. I was stressed about how to do this as well, all for nothing, it's just that I had never had to configure or load OSA cards before. OSA ignorance on my part I guess. The cards seem to get configured just fine when VTAM and TCP come up. We didn't have to manually load or configure anything with them, other than to make minor changes to VTAM and TCP parms because the physical address on the cards changed with the z9 (different PCHPID) and we happen to use this as part of the names for the cards in VTAM and TCP. One other thing we did was to make the cards 1000M instead of 100M as our local network was just upgraded to support gigabit. We was a simple change on the HMC (we don't trust auto negotiate, the default for the cards when the box was shipped to us). Not at all related to the new z9, just a good time to make this change here. b) How can i include new processors in the HMC GROUP. We're finding this process to be about as clear as mud. Three years ago when our z/890 was installed, the CE copied these definitions over from the last CPU. So the last time anyone here messed with setting these up was about 7 years ago. The CE didn't copy these over this time. We've still not gotten this set up the way we want, but are getting there. I'm sure we could copy them over, but this is a good time to start over from scratch and maybe set things up a bit differently. c) as we are moving all cables from old CPU to NEW CPU- we are migrating our HMC web server / OSA Integrated console configuration. will that work. I don't see any reason why this won't work. We've moved over the cables used by our test system to the z9 so far, channels dedicated to our production system get moved over tomorrow. We have checked PSP buckets and all fixes have been applied. Is there any other gottcha's we need to be concerned. I had checked PSP a two weeks ago, and found I was all set. Last week, I pulled current PSP buckets and found that two new PTFs were called for. So don't overlook pulling them again as you get closer to cutting over. The only other 'gotcha' so far was with a channel that had an ESCON converter on it with bus and tag cables to a 3174 and 3490 tape drives. When we moved this channel over, the converter's error light came on and the channel didn't come on line to the z9. Power cycling the converter didn't clear the problem, but what did work was to power off the converter, then IML the 3174, then power the converter back on. We have 4 more channels with converters on them to move tomorrow, so we'll have to wait and see how that goes. Feel free to contact me Monday to see how this weekend goes. Tom Chicklon -- 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
Re: CPC replacement
In a message dated 10/12/2007 10:39:20 A.M. Central Daylight Time, [EMAIL PROTECTED] writes: Have you gone through a Systems Assurance meeting with IBM's CEs, Sales, etc? All this is usually discussed and noted during the meeting, along with a detailed document passed around which goes over all the steps involved in the machine upgrade. Another box to check is third party software requiring keys based on CPUID and machine type. ** See what's new at http://www.aol.com -- 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
