brand new CF LPAR
Dear Lister We are replacing our mainframe i.e. Power off old mainframe, rip it apart, move power supply, I/O cages, OSA cards on to the new box and IML/IPL new CF and other LPARs. I have defined brand new Coupling datasets , ARM, BMPXMCDS, CFRM, SFM, LOGR, WLM dataset and have updated COUPLExx parmlib members. Are there other gottchas I should look out for. Our target is to Activate CF partition and IPL production LPAR in parallel sysplex ASAP after HW migration. All help is appreciated. I have gone through RTFM - setting up sysplex , CFSIZER tool etc. Regards, Munif. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: brand new CF LPAR
Just to add to my previous request, I have to define new coupling facility datasets to enbale support for newer protocols and do not know **yet** how to pouplate them with our exisitng sysplex policies.. May I IPL an LPAR (z/OS 1.13) with the new coupling facility datasets and then definine & activate (old) policies.. will it work?.. thanks again.. Munif -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: brand new CF LPAR
When you define your CFRM policy using IXCMIAPU you can point to your newly created CFRM CDS as Such: DATA TYPE(CFRM) REPORT(YES) DSN(Your newly created CFRM CDS name) DEFINE POLICY NAME(policyname here) REPLACE(YES) Etc.. That populates the newly created CFRM CDS with the policy(ies) that point to the new coupling facilities. In your COUPLExx member you can simply specify the new CFRM data sets as well as the POLICY you want to use by specifying CFRMPOL() where is your new policy name as specified by the IXCMIAPU job. The above is an example of only how to populate an inactive CFRM dataset. The DSN keyword on the DATA statement is what you need. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On > Behalf Of Munif Sadek > Sent: Monday, April 16, 2012 09:08 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: brand new CF LPAR > > Just to add to my previous request, I have to define new coupling facility > datasets to enbale support for newer protocols and do not know **yet** > how to pouplate them with our exisitng sysplex policies.. May I IPL an LPAR > (z/OS 1.13) with the new coupling facility datasets and then definine & > activate (old) policies.. will it work?.. > > thanks again.. Munif > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: brand new CF LPAR
I've lost track of the original postings in this thread, but I have this suggestion: never IPL an entire sysplex into a new XCF-anything unless you absolutely have no other choice. It's always preferable to move dynamically into a new XCF-something with at least one member running on the old one. It's (almost always?) possible to define a new thing in advance and migrate to it via SETXCF commands. This may mean defining a currently nonexistent resource ahead of time. XCF will tolerate a new thing it can't find yet as well as later tolerate an old thing it no longer find. Just clean up definitions at the very end to reflect the new environment. In the case of control data sets, create new ones with modern attributes, then SETXCF-migrate to them. By the time an actual hardware replacement occurs, new things should already be defined to the existing sysplex. The danger in cold starting with new components is that there's no way to test the process in advance, and falling back to a known environment may be complicated beyond reasonable resolution. . . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Jihad Kawkabani To: IBM-MAIN@bama.ua.edu Date: 04/16/2012 12:05 PM Subject:Re: brand new CF LPAR Sent by:IBM Mainframe Discussion List When you define your CFRM policy using IXCMIAPU you can point to your newly created CFRM CDS as Such: DATA TYPE(CFRM) REPORT(YES) DSN(Your newly created CFRM CDS name) DEFINE POLICY NAME(policyname here) REPLACE(YES) Etc.. That populates the newly created CFRM CDS with the policy(ies) that point to the new coupling facilities. In your COUPLExx member you can simply specify the new CFRM data sets as well as the POLICY you want to use by specifying CFRMPOL() where is your new policy name as specified by the IXCMIAPU job. The above is an example of only how to populate an inactive CFRM dataset. The DSN keyword on the DATA statement is what you need. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On > Behalf Of Munif Sadek > Sent: Monday, April 16, 2012 09:08 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: brand new CF LPAR > > Just to add to my previous request, I have to define new coupling facility > datasets to enbale support for newer protocols and do not know **yet** > how to pouplate them with our exisitng sysplex policies.. May I IPL an LPAR > (z/OS 1.13) with the new coupling facility datasets and then definine & > activate (old) policies.. will it work?.. > > thanks again.. Munif -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: brand new CF LPAR
Thank you all. Mr Kawkabani, I will use CFRMPOL to refer to newly created policy. What about ARM and SFM policies that I have created using IXCMIAPU and are named differently. How can I use them. Still searching for how to create new CDS, BPXMCDS, LOGR (hundreds of structures)and WLM policies and how to make system to use them right from the IPL.. Mr Robinson, My problem is I have only one ICF partition on each boxes (Old and New) and will not have cross coupling facility links. Both of the CF names are COUPL01. Can I format CFRM Policy with duplicate CF NAME COUPL01 for each process types (2818 and 2086, serial number will remain the same). If it is possible I can use same CFRM policy and before shutting down the last LPAR for processor migration, I can change CF configuration to match the new processor. I am planning to bring in sandbox LPAR in the plex first and should be able to use FORCE command to get the Coupling facility correct before bringing in any proper systems in the PLEX..i do agree its risky and need guidance. Thaks once again for you valuable suggestion, its much appreciated.. Regards, Munif. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: brand new CF LPAR
Each structure definition in the CFRM policy requires a PREFLIST to indicate where to allocate the structure. The PREFLIST contains one or more names as defined at the top of the policy. Although IBM recommends that NAME match the CF LPAR where it resides, that correspondence is not required. (I never even saw that recommendation until just now when I looked in the book.) For 15 years we have always used NAME to match the CEC because we name ICF LPARs by the sysplex to which they belong. That is, sysplex X will use LPAR CFPLEXX on all participating CECs. NAME would not be unique if we tried to use the ICF LPAR name. Bottom line is that NAME can be anything you choose as long as it follows the syntax rules. I wish I could tell you that I have done this exact same thing, but it should work fine. *Add* a new CF NAME to your policy like this: CF NAME(some-unique-name-of-your-choosing) TYPE(new-CEC-type) SEQUENCE(new-serial-number) PARTITION(new-LPAR-number) ... For each structure, include PREFLIST(old-name,new-name). Today only old-name will be found at IPL, so all structures will allocate there. After installing the new box, only new-name will be found, so that's where all structures will allocate. You will be just fine today and after the install. It can't hurt to try this now. If the CFRM policy compiles OK, you're 80% of the way there. Then activate the policy: SETXCF START,POL,TYPE=CFRM, POLNM=new-policy-name. If it activates with no errors, you're pretty much guaranteed that the same policy will work fine with the new CEC in place barring typos in CF definition. When you're all done, remove old-name from your policy. We've always had multiple CECs, but the principle is the same. We recently replaced both CECs on the floor using a similar strategy. At no point did we have to IPL into an untested configuration. . . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Munif Sadek To: IBM-MAIN@bama.ua.edu Date: 04/16/2012 10:21 PM Subject:Re: brand new CF LPAR Sent by:IBM Mainframe Discussion List Thank you all. Mr Kawkabani, I will use CFRMPOL to refer to newly created policy. What about ARM and SFM policies that I have created using IXCMIAPU and are named differently. How can I use them. Still searching for how to create new CDS, BPXMCDS, LOGR (hundreds of structures)and WLM policies and how to make system to use them right from the IPL.. Mr Robinson, My problem is I have only one ICF partition on each boxes (Old and New) and will not have cross coupling facility links. Both of the CF names are COUPL01. Can I format CFRM Policy with duplicate CF NAME COUPL01 for each process types (2818 and 2086, serial number will remain the same). If it is possible I can use same CFRM policy and before shutting down the last LPAR for processor migration, I can change CF configuration to match the new processor. I am planning to bring in sandbox LPAR in the plex first and should be able to use FORCE command to get the Coupling facility correct before bringing in any proper systems in the PLEX..i do agree its risky and need guidance. Thaks once again for you valuable suggestion, its much appreciated.. Regards, Munif. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
