Thanks, @Rob. Following your advice more or less I changed to subpool 35 and it is working like a champ.
I stuck with my original design of doing a subpool FREEMAIN after every 10 calls. Old "efficiency" habits die hard. But I do hear you. If I had done "regular" FREEMAINs instead of subpool FREEMAINs then all of this anguish would have been avoided. The "amount of work" is not bad. I am retrieving 169 RACF profiles and doing a whole lot of other stuff and the whole thing takes .03 CPU seconds on a zPDT. In a perfect world z/OS would have a service "hey, please assign me a unique subpool." Charles On Sat, 31 Aug 2024 15:28:23 +0000, Rob Scott <[email protected]> wrote: >Considering the amount of work that RAdmin is doing on your behalf, issuing a >FREEMAIN for each request does not seem a huge overhead (percentage wise). > >I just don't like the idea of entire subpool release in the normal operation >path, just seems like a problem waiting to happen. > >I also prefer to supply buffer and length parameters to services, but like >you, I have code that has to call RACF in this fashion. > >As to choosing subpool numbers for uniqueness, I use a range in the 30s, 40s >or so to attempt to make any leaks easier to find in IPCS or interactively >using the SDSF JM action on DA. I then subdivide that range to distinguish >usage, for example buffers versus product control blocks. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
