Re: Resetting QABNORMSW System Value

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

Jerry

There is a message, I think, that appears in the history log when a 
system value is changed. Maybe that also applies to this automatic 
change and could give you a very close timeframe.

Yeah, CPF1805.

Vern

Jerry Adams wrote:
> I hit Enter before I added that I still have no idea why the QABNORMSW value was '1' (abnormal).  I did write a program to run daily that will check the value and, if the value = '1', print a report on my printer.  Maybe then I'll have a better window for an investigation.  But Murphy says, "It'll never happen while you're watching."
>
> 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
>