I was assuming that there's already a macro or function call that handles accesses to the common storage and that a modification of same would be required in order to have a recovery environment established.
Also, the statement regarding accessing page-protected storage seems to imply that page-protected areas are backed by fixed frames. Is that so? Keven On Mar 6, 2016, at 07:20, Peter Relson <[email protected]> wrote: >> You could possibly page-protect the storage and use a recovery routine >> to drive the table storage monitoring and/or read/write functionality. > > 'fraid not, since there is no way to have *your* recovery routine in place > for *their* work unit that is doing the accessing. > > FWIW, if someone is truly interested in accessing page-protected storage, > and authorized, they can get the real address and use that. > > Peter Relson > z/OS Core Technology Design
