Re: Defining CFP in HCD
I've included them in mine without any problems. The only downside I can think of offhand would be if you were adding another ICF to CPUH as only one ICF per CFP is allowed in the access list. Regards, Kevin -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Larry Kraus Sent: Wednesday, February 22, 2006 8:24 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Defining CFP in HCD I have two CPUs. CPUH and CPUG. Each CPU has two mvs partitions and one ICF. In my example, CPUH has LPAR1, LPAR2, and COUPLE0H. When defining the CFP chpid on CPUH ( which will be used to communicate with CPUG), should COUPLE0H be in the partition access list. Or should it be defined like a CFS with only the MVS partitions in the access list. Disclaimer: This e-mail message is intended only for the personal use of the recipient(s) named above. If you are not an intended recipient, you may not review, copy or distribute this message. If you have received this communication in error, please notify us immediately by e-mail and delete the original message. This e-mail expresses views only of the sender, which are not to be attributed to Rite Aid Corporation and may not be copied or distributed without this statement. -- 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
Re: Defining CFP in HCD
Larry Kraus wrote: I have two CPUs. CPUH and CPUG. Each CPU has two mvs partitions and one ICF. In my example, CPUH has LPAR1, LPAR2, and COUPLE0H. When defining the CFP chpid on CPUH ( which will be used to communicate with CPUG), should COUPLE0H be in the partition access list. Or should it be defined like a CFS with only the MVS partitions in the access list. What machines do you have ? CFP is not available for 9672's (and older). I assume you have z/machines. You should define CHPids as CFP. Those CFPs can be shared or not, your choice. Each chpid can work as sender and receiver concurrently (that means shared between MVS and CF LPARs). Sometimes folks decide not to share the chpids for performance reasons. The devil is in the details. Do all the partitions belong to same sysplex ? How many channels do you have ? -- 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
Re: Defining CFP in HCD
I hope the diagram below looks OK. Assume two boxes each with (at least) one MVS and one ICF, all belonging to the same sysplex. Along with internal connection to its 'local' ICF, each MVS needs an external connection to the ICF in the other box. With ICF, you should also implement system managed duplexing to guard against catastrophic failure in a CEC, which would cause loss of structure data in the CF as well as in-storage copies in the now dead MVS. This requires an ICF-ICF connection. The diagram illustrates three separate links. However, since all the links connect LPARs in the same two boxes, there is an opportunity to EMIF the physical links for multiple logical connections. In particular, the ICF-ICF connection can use the same physical link as the MVS-ICF connections. We overlooked this possibility until Health Checker chided us for not making full use of the links. HC detected that links were defined but not included in all possible access lists. There should still be multiple links for redundancy and performance of course, but the idea is to make as many logical connections as possible out of the physical links. CPU1 CPU2 | MVS | | MVS | | | --|-| | | | ! | | | | | ! | | | |-| ! | |-| | ICF |-- ==| ICF | | |.| | . . JO.Skip Robinson Southern California Edison Company SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [EMAIL PROTECTED] IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 02/22/2006 08:23:49 AM: I have two CPUs. CPUH and CPUG. Each CPU has two mvs partitions and one ICF. In my example, CPUH has LPAR1, LPAR2, and COUPLE0H. When defining the CFP chpid on CPUH ( which will be used to communicate with CPUG), should COUPLE0H be in the partition access list. Or should it be defined like a CFS with only the MVS partitions in the access list. -- 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
