Whilst dynamically adding common storage objects such as subsystems and executables is commonplace, well used and understood, removing them is much trickier to do safely outside of a test/sandpit environment.
Knowing with 100% certainty that no other UOW is about to reference the memory that you have just released is difficult in the general case. Rob Scott Rocket Software Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Joseph Reichman <[email protected]> Sent: Sunday, August 11, 2024 2:33:57 PM To: [email protected] <[email protected]> Subject: Re: Resource manager for subsystem EXTERNAL EMAIL Esteem took the words out of my mouth what I’m looking for What is called RFE request for enhancement Maybe a parm on the SETSSI DELETE,PROG= > On Aug 11, 2024, at 9:29 AM, Joseph Reichman <[email protected]> wrote: > > Doesn’t that require an ipl > >> On Aug 11, 2024, at 7:35 AM, [email protected] wrote: >> >> ,I have found this thread interesting, and what I believe is needed >> is a SSI ROLLBACK or UNDO function. So that in the ESTAE/ESTAEX routine >> or in the init routine itself the "system" would remove any changes made >> SSCVT, SSVT, Remove the SSID etc. >> . >> This may not help the original poster with respect to a Resource >> Manager..Paul >> . >> >> ---------- Original Message ---------- >> From: Colin Paice <[email protected]> >> To: [email protected] >> Subject: Re: Resource manager for subsystem >> Date: Sun, 11 Aug 2024 08:31:52 +0100 >> >> I'm a bit rusty in this area. >> >> From the subsystem vector table (SVCCT?) there is an anchor field for your >> subsystem use. I assume that you are using this to anchor all of the >> storage you allocate, and set flags on anything you change. >> >> While you are debugging your code, you could have something in your >> initialisation code which checks these fields and resets them. >> If in debug_mode then >> do >> if my anchor -> a storage block I allocated then >> do >> ?wto "releasing my block " >> ? storage release... >> end >> if anchor.lockobtained then >> do >> ?wto "releasing the lock" >> ?... >> end >> /* start with a clean system...*/ >> The same logic could be done if you are using name token services to store >> pointers >> >> Colin >> >> >> >> >>> On Sun, 11 Aug 2024 at 02:17, Joseph Reichman < >>> [email protected]> wrote: >>> >>> Gut voch >>> >>> I’m debugging a subsystem so I run the init >>> It allocates resources latch CSA and other things >>> >>> Would be nice if I want start from scratch that I don’t have to ipl >>> >>> Thanks >>> >>>> On Aug 10, 2024, at 3:13 PM, Binyamin Dissen < >>> [email protected]> wrote: >>>> >>>> On Fri, 9 Aug 2024 12:40:20 -0400 Joseph Reichman >>>> <[email protected]> wrote: >>>> >>>> :>In deleting a subsystem is there a way to clean up storage that the >>> initialization routine established such as CSA >>>> >>>> :>I guess I could always do an ATTACH on the subsystem initialization >>> routine and >>>> :>And have a RESMGR for that TCB >>>> >>>> Do you have your init routine waiting for a shutdown request? Really bad >>> idea. >>>> :>Just wondering if there was a simpler way >>>> >>>> :>When I do a SETSSI DELETE the CSA that the initialization routine >>> acquires remains there >>>> >>>> What are you concerned about? >>>> >>>> The init routine failing? If so, a simple ESTAE(X) should be able to do >>> the >>>> cleanup. >>>> >>>> When removing your subsystem? Why not simply do it from there? >>>> >>>> What problem are you trying to solve? >>>> >>>> -- >>>> Binyamin Dissen <[email protected]> >>>> http://www.dissensoftware.com<http://www.dissensoftware.com> >>>> >>>> Director, Dissen Software, Bar & Grill - Israel >>>> >>>> ---------------------------------------------------------------------- >>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to [email protected] with the message: INFO IBM-MAIN >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >>> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ================================ Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
