I tried the force, since it was showing as an active connection not in a failed-persistent state, the force command wasn't accepted. I did need to perform a sysplex IPL and shutdown/activate the 2 CF lpars too before bringing things up.
Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, October 28th, 2021 at 12:26 AM, Barbara Nitz <nitz-...@gmx.net> wrote: > > A D XCF command isn't showing the system active.The ISGLOCK#SYSA connector > > is showing active to structure ISGLOCK > > From the other system, try forcing the connection of ISGLOCK#SYSA to the CF. > Take a dump from the other system of the XCF address space that also includes > the ISGLOCK structure when SYSA is fenced. Doesn't matter which system you > use. This sounds like a serious bug and you should have documentation. > > Try to rebuild everything out of the CF that houses ISGLOCK to the other CF > that you hopefully have. Then check the connection again, it should be gone. > > All else failing, reset the CF lpar (power off/power on that LPAR). That will > cost you all systems in the plex (assuming there're more than 2) and you will > need to IPL the complete sysplex. And use a freshly formatted primary CFRM > dataset to be on the safe side. Start that using the CFRM parm in couplexx. > > HTH, Barbara > > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > 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
