Re: Is ISGENQ a bit pricey?
W dniu 27.11.2020 o 14:35, Peter Relson pisze: It seems reasonable that it would in a real sysplex. This question and the original post make it sound like the poster's system was not in a sysplex. The display showed that it is in a sysplex. Is that not a "real sysplex"? My understanding: "real sysplex" - properly configured and tuned Parallel Sysplex with GRS STAR, etc. "not real sysplex" - somehow configured sysplex or parallel sysplex with lack of resources, GRS ring. Maybe good for some development or functional tests, but from performance point of view... Of course this is my interpretation of someone's words. Nothing more. I can be wrong. -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Prosta 18, 00-850 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2020 r. wynosi 169.401.468 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Prosta 18, 00-850 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169.401.468 as at 1 January 2020. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is ISGENQ a bit pricey?
>It seems reasonable that it would in a real sysplex. This question and the original post make it sound like the poster's system was not in a sysplex. The display showed that it is in a sysplex. Is that not a "real sysplex"? Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is ISGENQ a bit pricey?
On 2020-11-24 14:11 PM, Kirk Wolf wrote: 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. The doc you linked shows the resource as: |ENQ SPFEDIT,rname,E,52,SYSTEMS so you should use the identical qname, rname and scope for your ENQ. As Ed pointed out in another message, it looks like you have GRS ring mode set up on your system, and you are running a single system. You might get some benefits from changing GRS=RING to GRS=NONE. | On 2020-11-26 15:10 PM, Tony Harminc wrote: But SCOPE=SYSTEMS isn't a different namespace such that a competing program within the same system won't see it if it asks for SCOPE=SYSTEM. Sorry, incorrect. "Note that the control program considers a resource with a SYSTEMS scope to be different from a resource represented by the same qname and rname but with a scope of STEP or SYSTEM." https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa600/iea3a6_Defining_the_scope_of_a_resource.htm -- Regards, Gord Tomlin Action Software International (a division of Mazda Computer Corporation) Tel: (905) 470-7113, Fax: (905) 470-6507 Support: https://actionsoftware.com/support/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is ISGENQ a bit pricey?
On Tue, 24 Nov 2020 at 14:12, Kirk Wolf wrote: > > 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: OK. But SCOPE=SYSTEMS isn't a different namespace such that a competing program within the same system won't see it if it asks for SCOPE=SYSTEM. (I'm speaking of obtaining an ENQ here - not of explicitly scanning for existing ones.) In other words, if you have just the one system, I can't see any reason to be specifying SYSTEMS. If ISPF has ENQ'd using SYSTEMS, your program using SYSTEM will still wait for it. And the other way round. > 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? Yes, it is. But for your situation, who cares; if you have neither GRS nor a Sysplex, then just use SYSTEM. Of course you might want the same code to work safely in sharing environments, so you can either test for the environment, or better, leave the management of cross-system stuff to whoever configures these things on the target (customer?) system. SYSTEM level ENQs can be filtered by name, selectively promoted to SYSTEMS, and so on. > BTW: with SCOPE=SYSTEM, it is blazing fast. So my suspicion is that you do actually have more than one system sharing. But why, if it's IBM's Dallas setup in a VM? Tony H. > On Tue, Nov 24, 2020 at 12:48 PM Tony Harminc wrote: > > > On Tue, 24 Nov 2020 at 13:39, Kirk Wolf 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is ISGENQ a bit pricey?
My question is really not about tuning my system, but whether an ENQ for SCOPE=SYSTEMS is normally takes a bit of time? It seems reasonable that it would in a real sysplex. In my particular case: - loading 111 members to a PDS: 0.2 seconds - with SCOPE=SYSTEMS ENQ for each member: 3 seconds. - with SCOPE=SYSTEM ENQ for each member: 0.25 seconds In all cases, I have a DSN-level ISPF enqueue, so it's not a matter of corrupting the dataset - only whether a user with an edit session open on a member will be respected or ignored. On Wed, Nov 25, 2020 at 1:01 PM Mark Jacobs < 0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote: > Maybe try RESMIL=OFF too. > > If you specify RESMIL=OFF, the RSA-message residency time is set to zero > and global resource serialization does no tuning. If you specify RESMIL=0, > the system tunes the residency time in a range with a minimum of zero. > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com > > ‐‐‐ Original Message ‐‐‐ > > On Wednesday, November 25th, 2020 at 12:55 PM, Ed Jaffe < > edja...@phoenixsoftware.com> wrote: > > > On 11/24/2020 12:09 PM, Kirk Wolf wrote: > > > > > D GRS > > > > > > RESPONSE=S0W1 > > > > > > ISG343I 14.07.42 GRS STATUS 495 > > > > > > SYSTEM STATE SYSTEM STATE > > > > > > S0W1 ACTIVE > > > > > > GRS RING MODE INFORMATION > > > > > > RESMIL: 10 > > > > > > TOLINT: 180 > > > > > > SYNCHRES: YES > > > > > > ENQMAXU: 16384 > > > > > > ENQMAXA: 25 > > > > > > AUTHQLVL: 2 > > > > > > MONITOR: NO > > > > > > GRSMON: NONE > > > > > > D XCF > > > > > > RESPONSE=S0W1 > > > > > > IXC334I 14.08.07 DISPLAY XCF 497 > > > > > > SYSPLEX SVSCPLEX: S0W1 > > > > > > SYSPLEX INITIALIZATION TIME: 11/17/2020 09:41:16.129505 > > > > Ring mode. It's been a long, long time. > > > > I took a look at our stand-alone systems and saw that we code RESMIL(0) > > > > on GRSDEF in GRSCNF00. > > > > Not sure if that will help, but it might be worth a shot... > > > > > > > > > Phoenix Software International > > > > Edward E. Jaffe > > > > 831 Parkview Drive North > > > > El Segundo, CA 90245 > > > > https://www.phoenixsoftware.com/ > > > > > > > --- > > > > This e-mail message, including any attachments, appended messages and the > > > > information contained therein, is for the sole use of the intended > > > > recipient(s). If you are not an intended recipient or have otherwise > > > > received this email message in error, any use, dissemination, > distribution, > > > > review, storage or copying of this e-mail message and the information > > > > contained therein is strictly prohibited. If you are not an intended > > > > recipient, please contact the sender by reply e-mail and destroy all > copies > > > > of this email message and do not otherwise utilize or retain this email > > > > message or any or all of the information contained therein. Although this > > > > email message and any attachments or appended messages are believed to be > > > > free of any virus or other defect that might affect any computer system > into > > > > which it is received and opened, it is the responsibility of the > recipient > > > > to ensure that it is virus free and no responsibility is accepted by the > > > > sender for any loss or damage arising in any way from its opening or use. > > > > > - > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN
Re: Is ISGENQ a bit pricey?
Maybe try RESMIL=OFF too. If you specify RESMIL=OFF, the RSA-message residency time is set to zero and global resource serialization does no tuning. If you specify RESMIL=0, the system tunes the residency time in a range with a minimum of zero. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com ‐‐‐ Original Message ‐‐‐ On Wednesday, November 25th, 2020 at 12:55 PM, Ed Jaffe wrote: > On 11/24/2020 12:09 PM, Kirk Wolf wrote: > > > D GRS > > > > RESPONSE=S0W1 > > > > ISG343I 14.07.42 GRS STATUS 495 > > > > SYSTEM STATE SYSTEM STATE > > > > S0W1 ACTIVE > > > > GRS RING MODE INFORMATION > > > > RESMIL: 10 > > > > TOLINT: 180 > > > > SYNCHRES: YES > > > > ENQMAXU: 16384 > > > > ENQMAXA: 25 > > > > AUTHQLVL: 2 > > > > MONITOR: NO > > > > GRSMON: NONE > > > > D XCF > > > > RESPONSE=S0W1 > > > > IXC334I 14.08.07 DISPLAY XCF 497 > > > > SYSPLEX SVSCPLEX: S0W1 > > > > SYSPLEX INITIALIZATION TIME: 11/17/2020 09:41:16.129505 > > Ring mode. It's been a long, long time. > > I took a look at our stand-alone systems and saw that we code RESMIL(0) > > on GRSDEF in GRSCNF00. > > Not sure if that will help, but it might be worth a shot... > > > > Phoenix Software International > > Edward E. Jaffe > > 831 Parkview Drive North > > El Segundo, CA 90245 > > https://www.phoenixsoftware.com/ > > > --- > > This e-mail message, including any attachments, appended messages and the > > information contained therein, is for the sole use of the intended > > recipient(s). If you are not an intended recipient or have otherwise > > received this email message in error, any use, dissemination, distribution, > > review, storage or copying of this e-mail message and the information > > contained therein is strictly prohibited. If you are not an intended > > recipient, please contact the sender by reply e-mail and destroy all copies > > of this email message and do not otherwise utilize or retain this email > > message or any or all of the information contained therein. Although this > > email message and any attachments or appended messages are believed to be > > free of any virus or other defect that might affect any computer system into > > which it is received and opened, it is the responsibility of the recipient > > to ensure that it is virus free and no responsibility is accepted by the > > sender for any loss or damage arising in any way from its opening or use. > > - > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is ISGENQ a bit pricey?
On 11/24/2020 12:09 PM, Kirk Wolf wrote: D GRS RESPONSE=S0W1 ISG343I 14.07.42 GRS STATUS 495 SYSTEMSTATE SYSTEMSTATE S0W1 ACTIVE GRS RING MODE INFORMATION RESMIL: 10 TOLINT:180 SYNCHRES: YES ENQMAXU: 16384 ENQMAXA:25 AUTHQLVL:2 MONITOR:NO GRSMON: NONE D XCF RESPONSE=S0W1 IXC334I 14.08.07 DISPLAY XCF 497 SYSPLEX SVSCPLEX: S0W1 SYSPLEX INITIALIZATION TIME: 11/17/2020 09:41:16.129505 Ring mode. It's been a long, long time. I took a look at our stand-alone systems and saw that we code RESMIL(0) on GRSDEF in GRSCNF00. Not sure if that will help, but it might be worth a shot... -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is ISGENQ a bit pricey?
D GRS RESPONSE=S0W1 ISG343I 14.07.42 GRS STATUS 495 SYSTEMSTATE SYSTEMSTATE S0W1 ACTIVE GRS RING MODE INFORMATION RESMIL: 10 TOLINT:180 SYNCHRES: YES ENQMAXU: 16384 ENQMAXA:25 AUTHQLVL:2 MONITOR:NO GRSMON: NONE D XCF RESPONSE=S0W1 IXC334I 14.08.07 DISPLAY XCF 497 SYSPLEX SVSCPLEX: S0W1 SYSPLEX INITIALIZATION TIME: 11/17/2020 09:41:16.129505 On Tue, Nov 24, 2020 at 1:56 PM Ed Jaffe wrote: > On 11/24/2020 10:39 AM, Kirk Wolf wrote: > > 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). > > What do you see when you issue these two commands? > > D GRS > D XCF > > -- > Phoenix Software International > Edward E. Jaffe > 831 Parkview Drive North > El Segundo, CA 90245 > https://www.phoenixsoftware.com/ > > > > > This e-mail message, including any attachments, appended messages and the > information contained therein, is for the sole use of the intended > recipient(s). If you are not an intended recipient or have otherwise > received this email message in error, any use, dissemination, distribution, > review, storage or copying of this e-mail message and the information > contained therein is strictly prohibited. If you are not an intended > recipient, please contact the sender by reply e-mail and destroy all copies > of this email message and do not otherwise utilize or retain this email > message or any or all of the information contained therein. Although this > email message and any attachments or appended messages are believed to be > free of any virus or other defect that might affect any computer system > into > which it is received and opened, it is the responsibility of the recipient > to ensure that it is virus free and no responsibility is accepted by the > sender for any loss or damage arising in any way from its opening or use. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is ISGENQ a bit pricey?
On 11/24/2020 10:39 AM, Kirk Wolf wrote: 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). What do you see when you issue these two commands? D GRS D XCF -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ This e-mail message, including any attachments, appended messages and the information contained therein, is for the sole use of the intended recipient(s). If you are not an intended recipient or have otherwise received this email message in error, any use, dissemination, distribution, review, storage or copying of this e-mail message and the information contained therein is strictly prohibited. If you are not an intended recipient, please contact the sender by reply e-mail and destroy all copies of this email message and do not otherwise utilize or retain this email message or any or all of the information contained therein. Although this email message and any attachments or appended messages are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the sender for any loss or damage arising in any way from its opening or use. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is ISGENQ a bit pricey?
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 wrote: > On Tue, 24 Nov 2020 at 13:39, Kirk Wolf 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Is ISGENQ a bit pricey?
On Tue, 24 Nov 2020 at 13:39, Kirk Wolf 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
