> > Change the subsystem name in the SSCT (perhaps change one character to lower > > case) and free everything. Of course, be careful that nothing is running in > > the code dynamically loaded.
Isn't it possible that the subsystem name occurs elsewhere and/or has been in some way added to a hashed lookup scheme this would break? And this hash scheme isn't a documented interface so it's don't touch or even look at. looking at SSCVT mapping: https://www.ibm.com/docs/en/zos/2.5.0?topic=xtl-sscvt-information 24 (18) ADDRESS 4 SSCTSYN HASH TABLE SYNONYM POINTER So there might be some sort of hash table indexing these allowing z/OS services to avoid a linear search down the SSCT chain. I think that the SSCT is a creation only item, no delete, and now should only be created via the z/OS services designed to create it. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
