I run monoplexs. Like I expect most other small shops. 4 LPARS, only shared DASD, no CTC connections. There are TCPIP Hipersocket links, but as far as I know, XCF is not aware of these links. What/Who are the typical users of XCF signaling in a monoplex. How would I know if they are experiencing degraded or inefficient signaling?
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On > Behalf Of Vernooij, CP - SPLXM > Sent: Saturday, March 31, 2012 2:40 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: New z/OS 1.13 Health Checks - Friday Rant > > "R.S." <r.skoru...@bremultibank.com.pl> wrote in message > news:<4f776fe9.80...@bremultibank.com.pl>... > > W dniu 2012-03-30 16:24, Mark Brooks pisze: > > > Hi, > > > The XCF signalling services are available in all sysplex > > > environments, including monoplex. The rationale that motivates the > > > defining of transport classes applies to them all. > > > > What for? > > The classes are for traffic on sysplex links, are they? > > No links, no need for traffic priorities. > > > > > > -- > > Radoslaw Skorupka > > Lodz, Poland > > > > > > Read well: they are for XCF signalling links. Keep a couple of things > separated: > 1. XCF signalling is used between members that connect to an XCF group. > The advantage is that the members don't have to worry where the other > members are and how to reach them. XCF will take care of that. > 2. A members can be anywhere in a sysplex, so also on the same LPAR. > This means that XCF signalling is used/usable in a monoplex and that is why > signalling control and tuning is needed in any sysplex, also a monoplex. > 3. XCF will communicate via XCF signalling paths, which are internal within > the > lpar and via CF structures and/or CTC connections between LPARs and > machines. > > So, classes are not for sysplex links, but for XCF transportation. Maybe XCF > decides to sends messages over sysplex links, maybe not. > > Kees. > ******************************************************** > For information, services and offers, please visit our web site: > http://www.klm.com. This e-mail and any attachment may contain > confidential and privileged material intended for the addressee only. If you > are not the addressee, you are notified that no part of the e-mail or any > attachment may be disclosed, copied or distributed, and that any other > action related to this e-mail or attachment is strictly prohibited, and may be > unlawful. If you have received this e-mail by error, please notify the sender > immediately by return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission of > this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch > Airlines) is registered in Amstelveen, The Netherlands, with registered > number 33014286 > ******************************************************** > > > ---------------------------------------------------------------------- > 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
