Gabriel, 1) You should post to the list, not the newsgroup, if you want everybody to see your question.
2) Unlike ring mode, where every system sees all contention for global resources, in star mode, contention processing for resources only occurs on particular systems. This poses an ordering problem for resource contention notification. To ensure that contention notifications are properly ordered by a particular receiver, GRS forwards all the contention events to a single system (the contention notifying system) to serialize their delivery. Scott Fagen z/OS Core Technology Design IBM Poughkeepsie Gabriel Tully wrote: > Hello, > > I'm trying to learn more about GRS. I get the basics but I ran > across something that I can't find any doc about. Part of the output > of "D GRS,SYSTEM", when in STAR mode, displays: > THE CONTENTION NOTIFYING SYSTEM IS xxxx - where xxxx is your system > name. What exactly does this mean? I have been assuming that that's > the system where all the output was batched and sent from. Also, does > latch contention act like ISGLOCK requests in that the command to > display the requests or latch contention must be entered on the system > that is experiencing the request/latch contention? That is what's its > scope in a syspelx? > > System Level: z/OS 1.4 @ RSU 0502 > Processor : IBM 2064-1C7 (z/900) Mode: 64-bit > > Appreciative, > > Gabriel > ---------------------------------------------------------------------- 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
