RE: Resetting QABNORMSW System Value

[Jerry Adams <Jerry@xxxxxxxxxxxxxxx>]

Rob,

Sorry to be so long getting back; invoicing blew off (user problem - but then I wasn't checking for the condition, but that's been fixed now).  

I really didn't see anything out of the ordinary when I printed the DSPLOG.  There were a few information messages with severity '80', but we've had these particular errors for years.  Plus they are listed about 8-9 hours *after* the PWRDWNSYS.

I will try another IPL later this week.  

The only reason that I looked at it was because I have a cume (V5R4) to apply to this server in a week or two.  I only recall having to do two IPL's after a PTF apply once, and that *may* have been because of the QABNORMSW value (or one of those rare situations when IBM required it - can't remember now).

Thanks.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email:  jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, January 25, 2010 10:33 AM
To: Midrange Systems Technical Discussion
Subject: RE: Resetting QABNORMSW System Value

Jerry,

If you had a job prior to your IPL end abnormally, you'll see the 
QABNORMSW turned on.  If you then end another job abnormally then it will 
still be on after your next IPL.

Maybe if, instead, you do
CHGIPLA STRPRTWTR(*NO) STRRSTD(*YES)
PWRDWNSYS DELAY(120) RESTART(*YES) IPLSRC(B)
check QABNORMSW and if still on repeat
CHGIPLA STRPRTWTR(*NO) STRRSTD(*YES)
PWRDWNSYS DELAY(120) RESTART(*YES) IPLSRC(B)
This time it should not be on.  I have something similar to this in my 
instructions when I IPL to apply ptf's.

The point being that
1 - it may take two IPLs to get a clean one.
2 - another job can ENDJOBABN causing this issue.

I'd review the one posters suggestion on the DSPLOG.


Rob Berendt