"R.S." <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > Vernooy, C.P. - SPLXM wrote: > > > "R.S." <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > > > >>You can use GRS across monoplexes. > >>It does't require Parallel Sysplex. > >>Base Sysplex is recommended, but also not required. > >>For non-sysplex GRS, you native GRS CTC communication: BCTC devices. > >>Usually GRS uses XCF communication - that means Base Sysplex. > >> > >>BTW: I don't know what Shane mean, but it is feasible to share data > >>without GRS and without integrity exposures. > >> > >>-- > > > > > > I know what Shane means, you can share data without GRS if you know the > > integrity exposures. A lot is protected via Reserver/Release hardware > > reserves, but simple dataset protection works only with SYSDSN ENQs within > > each system and there is nothing to prevent simultaneous updates on two > > systems. GRSs (and MIM) function is to propagate these ENQs to the other > > system(s). However, you can workout a configuration where each system has > > its own Dasd such that exposures are minimized. > > You mean an application which issues ENQ,SCOPE=SYSTEM, but not RESERVE ? > > IMHO bad design, it should be > RESERVE and ENQ. > > ..but it is still circumvention to use ...GRS <g> > Just change place the resource on INCLUDE list, to convert SCOPE=SYSTEM > to > SCOPE=SYSTEMS. > You can do it on every monoplex, without connecting GRSes. > > --
No! Some basisc: ENQs and RESERVEs are two different beasts. ENQs serialize a resource within a system, RESERVEs cause the hardware to reserve the volume together with an ENQ in the local system (in fact a RESERVE macro is an ENQ macro with a UCB parameter). SYSDSN is an ENQ without a RESERVE, it is designed as such, you can like it or not. ENQs come in the flavours SYSTEM and SYSTEMS. The first is intended to stay within the system, the second is intended to be propagated to the other systems. But still, this ENQ propagation and has nothing to do with RESERVEs. If you think putting a resource in the INCLUDE list will transfer it to a RESERVE, you are wrong! Putting a RESERVE in the CONVERSION list, will transfer it into a normal ENQ over all systems. 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. ********************************************************************** ---------------------------------------------------------------------- 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
