On Monday, 11/16/2009 at 02:53 EST, Rob van der Heij <[email protected]> wrote:
> You're putting different traces in my mouth. It does not have to be a > bogus PGM New PSW. It can also be something happening in the program > check handler. A popular trick is when the old PSW is massaged in some > way before doing a LPSW to continue at a slightly different spot. Sorry. I thought I knew what you meant. :-) A program interrupt loop is detected when there is a program check and the current PSW is the "same" as the Program New PSW. This indicates that there is something wrong with Program New PSW or there's not a valid instruction at the address pointed to by the PNPSW. Alan Altmark z/VM Development IBM Endicott
