I'm doing ISPF-compatible member enqueues, while loading a bunch of members with BPAM/BSAM. I'm following the doc, which indicate SCOPE=SYSTEMS:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.f54pc00/isppcmmnamen.htm I guess that I don't understand the distinction between GRS and sharing within a SYSPLEX wrt SCOPE=SYSTEMS. I had assumed that SCOPE=SYSTEMS is not only GRS, but also for serializing across members of a sysplex. No? BTW: with SCOPE=SYSTEM, it is blazing fast. On Tue, Nov 24, 2020 at 12:48 PM Tony Harminc <[email protected]> wrote: > On Tue, 24 Nov 2020 at 13:39, Kirk Wolf <[email protected]> wrote: > > > ISGENQ > > REQUEST=OBTAIN, > > COND=YES, > > QNAME=QN,RNAME=RN,RNAMELEN=52, > > CONTROL=EXCLUSIVE, > > SCOPE=SYSTEMS, > > RETCODE=RC,RSNCODE=RSN, > > ENQTOKEN=MYTOK > > > I notice that Obtains takes about 14ms and Releases about 12ms, so 100 > > iterations is almost 3 seconds. > > > > I guess that makes sense with SCOPE=SYSTEMS, but I'm doing this on a > system > > that isn't on a sysplex (but it is running second level at IBM RDP). > > I don't understand why you have SCOPE=SYSTEMS... Are you sharing a > resource across systems that are not in a sysplex? This is possible > with GRS, but not common these days, and can lead to problems. That > you are running in a VM doesn't seem relevant. > > Tony H. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
