On Mon, Nov 16, 2009 at 6:19 PM, Alan Altmark <[email protected]> wrote:
>> As soon as I reply with >>r 00,sysp=00,clpa<< everything dies with a >> HCPGIR453W CP entered; program interrupt loop message. > > As Rob says, HCP453W indicates that the PROGRAM NEW PSW was corrupted or > otherwise not valid when a Program Interrupt (program check) occurred. > While it's fairly easy to find out what caused the fatal program > interrupt, it won't help to explain why the program new PSW is bad. You > can try #CP TRACE PROG RUN CMD D PSW PROG and then re-IPL. You will > likely get more than one hit, but the last one will be the fatal one and > you will will see from the output that the PNPSW is bogus. Wiping out of > the PNPSW isn't usually a surgical strike, but is more often part of the > larger mass destruction of low core (that's page 0 for you young > whippersnappers out there), usually from picking up an unexpectedly zero > pointer. 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. I expect MVS will do a lot of program checks and most of them being legitimate. What I suggested was to look at the PGM Old PSW to understand where it occurred and what type of program check it was. Rob Rob van der Heij Velocity Software http://www.velocitysoftware.com/
