× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.