Re: Orphaned SYSDSN Enqueue
This sounds like a bug in RTM where the percolation was interrupted from RTM2 to RTM1 (order?) and the ECB post never occurred. This was in the z/OS 1.4 / 1.7 time frame. There was no way to force it from the system other than to either IPL or for the ECB post to occur (with something like an MVS monitor). I have had this happen on another 2.2 system.. and we just waited for the next IPL to clean it up. It only affected a single TSO user and there was a fairly workaround. HTH, Rob Schramm On Wed, Nov 10, 2021 at 6:26 PM Roger Suhr wrote: > You may have an address space with that ASID still in the system. You > should be able to display it, CANCEL it and FORCE it, (with ARM). Removing > that ASID on the system where it exists, should clear the ENQ. > > Sent from my Verizon, Samsung Galaxy smartphone > Get Outlook for Android<https://aka.ms/AAb9ysg> > > From: IBM Mainframe Discussion List on behalf > of Mark Jacobs <0224d287a4b1-dmarc-requ...@listserv.ua.edu> > Sent: Wednesday, November 10, 2021 8:57:10 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Orphaned SYSDSN Enqueue > > We have an orphaned SYSDSN enqueue that's preventing CICS from starting. > GRS shows it enqueued by the CICS STC that we're trying to startup. The > ASID that's being displayed is currently in use by a a different STC. > Outside of an IPL is there anyway to remove the enqueue from the sysplex? > > Mark Jacobs > > Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted > email. > > GPG Public Key - > https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com > > -- > 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: Orphaned SYSDSN Enqueue
You may have an address space with that ASID still in the system. You should be able to display it, CANCEL it and FORCE it, (with ARM). Removing that ASID on the system where it exists, should clear the ENQ. Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Android<https://aka.ms/AAb9ysg> From: IBM Mainframe Discussion List on behalf of Mark Jacobs <0224d287a4b1-dmarc-requ...@listserv.ua.edu> Sent: Wednesday, November 10, 2021 8:57:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Orphaned SYSDSN Enqueue We have an orphaned SYSDSN enqueue that's preventing CICS from starting. GRS shows it enqueued by the CICS STC that we're trying to startup. The ASID that's being displayed is currently in use by a a different STC. Outside of an IPL is there anyway to remove the enqueue from the sysplex? Mark Jacobs Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com -- 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: Orphaned SYSDSN Enqueue
It's not. I checked that first thing. We wound up needing to IPL the system. 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 Wednesday, November 10th, 2021 at 12:12 PM, Mickey Virdi wrote: > Is the owning ASID an INIT ASID, have you attempted to drain the init if it > is? > > > We have an orphaned SYSDSN enqueue that's preventing CICS from starting. > > GRS shows it enqueued by the CICS STC that we're trying to startup. The > > ASID that's being displayed is currently in use by a a different STC. > > Outside of > > > > an IPL is there anyway to remove the enqueue from the sysplex? > > > Mark Jacobs > > 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: Orphaned SYSDSN Enqueue
Is the owning ASID an INIT ASID, have you attempted to drain the init if it is? > We have an orphaned SYSDSN enqueue that's preventing CICS from starting. GRS > shows it enqueued by the CICS STC that we're trying to startup. The ASID > that's being displayed is currently in use by a a different STC. Outside of > an IPL is there anyway to remove the enqueue from the sysplex? >Mark Jacobs -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Orphaned SYSDSN Enqueue
We have an orphaned SYSDSN enqueue that's preventing CICS from starting. GRS shows it enqueued by the CICS STC that we're trying to startup. The ASID that's being displayed is currently in use by a a different STC. Outside of an IPL is there anyway to remove the enqueue from the sysplex? Mark Jacobs Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
