Jerry, I don't have the type of setup you have but I'll list a few things I
might look at.
Move the CONTENTION NOTIFYING SYSTEM from your TEST lpar to your MVSZ lpar,
assuming MVSZ is your production lpar. This process can add overhead to GRS
and on a small lpar it can be noticeable. The process will move around based
on which lpar gets IPLed and GRS will not move it back. So we issue the SETGRS
CNS=PR03,NP command on our PR03 lpar anytime it is IPLed.
Sample of what it looks like on the SYSLOG.
SETGRS CNS=PR03,NP
ISG364I CONTENTION NOTIFYING SYSTEM MOVED FROM SYSTEM TS03 TO SYSTEM
PR03. OPERATOR COMMAND INITIATED.
I'm going to guess that the ICF1 and ICF2 lpars may not be getting dispatched
as well as you might hope. You might see this in the response times of the CF
links or in requests getting switched from synchronous to asynchronous. So
that could affect how well they respond to things.
Another thing to think about is the size of your IGWLOCK00 structure. The size
will be different base on your environment as compared to what I have. I was
not the one to size our IGWLOCK00 structure so I'm not much help there.
You could try to move some of the XCF traffic off of the CFs and on to CTCs to
see if that helps any. Just a guess.
Also if the TEST lpar is not getting dispatched when needed that can cause
issues for things like GRS and XCF and their ability to respond to request.
I hope that some of this is helpful. Good luck.
Thanks..
Paul Feller
GTS Mainframe Technical Support
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Edgington, Jerry
Sent: Tuesday, June 02, 2020 12:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: XCF/GRS question [EXTERNAL]
We are running on single SYSPlex with two LPARs (Prod and Test) with 2 ICFs,
all running on the GPs. We are experiencing slowdowns, due to PROC-GRS on
Test, PROC-XCFAS on Prod. Weights are 20/20/20/80 for ICF1/ICF2/Test/Prod. We
have setup XCF Structures and FCTC for GRS Star
Higher Weight:
PROC-GRS 3.4 users
PROC-GRS 2.4 users
ENQ -ACF2ACB 100.0 % delay LOGONIDS
PROC-GRS 99.0 % delay
PROC-GRS 13.0 % delay
Lower weight:
PROC-XCFAS 14.1 users
PROC-XCFAS 13.1 users
PROC-XCFAS 99.0 % delay
PROC-XCFAS 45.0 % delay
PROC-XCFAS 16.0 % delay
PROC-XCFAS 11.0 % delay
PROC-XCFAS 33.0 % delay
PROC-XCFAS 77.0 % delay
PROC-XCFAS 45.0 % delay
GRSCNFxx:
GRSDEF MATCHSYS(*)
SYNCHRES (YES)
GRSQ (CONTENTION)
ENQMAXA(250000)
ENQMAXU(16384)
AUTHQLVL(2)
RESMIL(5)
TOLINT(180)
IEASYSxx:
GRS=STAR, JOIN GRS STAR
GRSCNF=00, GRS INITIALIZATION MEMBER
GRSRNL=00, GRS RESOURCE LIST
D GRS:
RESPONSE=TEST
ISG343I 13.38.49 GRS STATUS 604
SYSTEM STATE SYSTEM STATE
MVSZ CONNECTED TEST CONNECTED
GRS STAR MODE INFORMATION
LOCK STRUCTURE (ISGLOCK) CONTAINS 1048576 LOCKS.
THE CONTENTION NOTIFYING SYSTEM IS TEST
SYNCHRES: YES
ENQMAXU: 16384
ENQMAXA: 250000
GRSQ: CONTENTION
AUTHQLVL: 1
MONITOR: NO
Any advice or help on what I can do about these delays, would be great?
Thanks,
Jerry
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
Please note: This message originated outside your organization. Please use
caution when opening links or attachments.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
