By definition, the subject seems to me to be an oxymoron. An authorized address space has JSCBAUTH on. There can be no unauthorized code running in such a situatino. Now, if you meant a space in which JSCBAUTH is not on (perhaps it was on) and there are tasks that are supervisor state and/or system key and you want to give control to code that is problem state user key, then you should be using SYNCH(X). You might choose to SYNCH(X) to "yourself" and do a LINK(X) from there, or a LOAD / CALL or whatever. As I mentioned in a post on the ADRNAPF topic, once JSCBAUTH has been turned off, you must never turn it back on.
On a somewhat related note, although the cross-memory architecture supports authority-decreasing PCs, I believe it is the case that z/OS does not. It cannot stop you from creating them, but you should not be doing so. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
