On Mon, Dec 14, 2009 at 6:25 PM, Joe Reichman <[email protected]>wrote:
> It is A Stacking PC I was under impression that when PR executes at the end > of the PC rtn the OS puts the environment back to the way it was before the > PC rtn > > Was invoked > > The POST ASID is only a few instruction later don't know why the SYSUDUMP > says PRIMARY NOT EQUAL HOME > <http://bama.ua.edu/archives/ibm-main.html> > Technically the PR instruction hardware, not the OS, restores the PASN and SASN to the values they had when the PC was issued. If it just so happened that you were already running in a cross-memory address space (PASN <> HASN) when you issued YOUR stacking ss-PC then when your PC returns via a PR, you will faithfully be back in the state you were before the PC with primary not equal to home. Hence my point earlier about competely understanding your execution environment. This is a real world case I have seen many times. You can have server address spaces that call others that in turn call others so (BTW) when you're writing space switch routines, you cannot assume that you came "from" your home address space. You should also not make any assumptions about the SASN. Depending on what you put on the SASN keyword of the ETDEF ENTRY macro you will get a different cross memory state on entry to the PC. Starting from the top, what exactly are you trying to accomplish? -- This email might be from the artist formerly known as CC (or not) You be the judge. ---------------------------------------------------------------------- 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
