Binyamin wrote: <snip> I believe that you have a misunderstanding of what "shared subpools" are. </snip> I share Binyamin's belief.
Joseph R wrote: <snip> So if task B frees tasks A storage and it’s not shared I would get a B37 type error ? </snip> No, you get whatever you get when you reference freed storage. 0C4-xx is the most common. Sharing has no relevance to the behavior upon reference. <snip> I am now aware making sure the SDWALSED is set right on a retry if the abend was within a BAKR <snip> Another scary post. Fortunately, I think that RTM does not care if you do or do not change SDWALSED. A recovery routine should not set any of the non-retry-related fields; those fields are provided for diagnosis reasons. The system manages the linkage stack entry address, not you. SDWALSED is not even designated as a programming interface. You can set SDWALSLV to influence the behavior for retry (e.g., set it to 1 if you want the retry to be one linkage stack entry more than time-of-recovery-establishment). I think that its comment is pretty clear. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
