Re: Resetting QABNORMSW System Value

Sounds like a reasonable request....why haven't you opened a DCR yet?
<grin>

Charles

On Mon, Jan 25, 2010 at 2:16 PM, <rob@xxxxxxxxx> wrote:

Problem is, if you have this 80 type error 8-9 hours after every IPL then
every IPL will always be an abnormal ipl. Unless you do the second IPL
before the problem occurs.

What I'd like to see is if my NEXT IPL is going to be abnormal. Because
if it was then I'd do
CHGIPLA STRPRTWTR(*NO) STRRSTD(*YES)
PWRDWNSYS DELAY(120) RESTART(*YES) IPLSRC(B)
PWRDWNSYS DELAY(120) RESTART(*YES) IPLSRC(B)

That CHGIPLA before the first IPL ensures that the system starts in a
restricted state and getting to the point where you can do the second IPL
is much faster.

I'd like a better flag than doing the DSPLOG and checking for a level 80.
Hey, it might be longer between IPL's than the retention of QHST.


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jerry Adams <Jerry@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/25/2010 02:04 PM
Subject: RE: Resetting QABNORMSW System Value
Sent by: midrange-l-bounces@xxxxxxxxxxxx



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
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jerry Adams <Jerry@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 01/25/2010 10:32 AM
Subject: RE: Resetting QABNORMSW System Value
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Well, not much of anything in the History; at least not that I can see.
There is a message right after the IPL (on Friday) started and after the
file systems are mounted: Previous ending abnormal, reason code 1. (1 -
The system ended a job abnormally.) But I already knew that.

There is one suspect message: Vary Configuration error occurred during
IPL. The detailed explanation says to display the QSYSARB job log. But
that only shows me that some devices (not attached to controllers) could
not be varied on.

I displayed the value of QABNORNSW immediately after the IPL (PWRDWNSYS
with *IMMED and Restart(*Yes)) finished on Friday, and it was '1' at that
time. I displayed it again this morning (hoping against hope that the
system just needed some time to assess the situation); it is still '1'.

I checked the archives before posting today. Lots of information about
what can cause the value to be '1' (usually ENDJOBABN). The only
"recovery" that I found was to re-IPL the system, as I did. I guess I
could re-IPL again tonight, but if Friday's IPL had no effect, I have to
reason to think that tonight's would. Is a re-IPL the only was to reset
QABNORNSW to '0'?

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 Stefan Tageson
Sent: Monday, January 25, 2010 7:42 AM
To: Midrange Systems Technical Discussion
Subject: RE: Resetting QABNORMSW System Value

So, anyway, how and when is the QABNORMSW system value reset?

QABNORMSW will be set or reset at system power down depending on if
command ENDJOBABN been used prior to power down.

Look in the history log around system restart and you should have
additional messages indicating the reason for the abnormal system end.


Regards



Stefan Tageson

AddconIT AB

Cell : +46 (0) 732 36 99 34

stefan.tageson@xxxxxxxxxxx

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.