In my experience a S0D6-027 implies that the LX owning address space has
terminated (normally or abnormally) but the program(s) issuing PC
instructions to that LX continue. I would review your design for
"terminating the LX owning address space and stopping the PC calls".
A simple test case that I use is to cancel the LX owner while driving
the programs that would issue the PC calls.
Ray Overby Key Resources, Inc. Ensuring System Integrity for z/Series™
www.kr-inc.com (312)574-0007
On 8/23/2013 06:46 AM, Robin Atwood wrote:
Our application very occasionally (once every few months) abends 0D6-027, which means a
PC instruction has caused a "Linkage second index translation exception". I am
wondering exactly what this is telling me since the auxiliary ASID being PCed to had been
active for some time and had processed several requests, ie, the PC had been working
perfectly well up until the abend. So what has gone bad? My understanding is that the PC
linkage information is kept in system control blocks so that should be OK. The PC number
we are calling is X'00017F00' which implies an ET index of X'F00'; is that sane? Any
hints gratefully received!
Robin
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
