On Thu, 24 May 2018 17:52:27 +0200, Peter Hunkeler wrote: > >Module reusability: >o Reenterable (reentrant). The module is designed for concurrent execution by >multiple tasks. If a reenterable module modifies its own data areas or other >shared resources in any way, appropriate serialization must be in place to >prevent interference between using tasks. > Is this from Program Management Guide?
This suggests a couple experiments: o Mark a program object RENT but not REFR. Code it to store into itself then restore the initial content. Serialize with a simple CS-STIMER loop. Any ABEND or program check should merit SR, even under OMVS. WAD? o LINK to such an object in two different processes, each invoked with _BPX_SHAREAS=MUST spawn(). Compare load addresses to see whether the instance is shared. If not shared it's a quality/performance matter, perhaps not SR. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
