|
wrote:
not much of anything in the History; at least not that I can see.
Try to DSPLOG with output *print for the time period between the two ipls.
Then scan the spoolfile for ' 80' ( blank followed by 80 ) which is the end
severity shown on a CPF1164 msg when ENDJOBABN is being used. If nothing
found try the same with severity 90. If nothing found - then I'm lost :)
Regards
Stefan Tageson
AddconIT AB
Cell : +46 (0) 732 36 99 34
stefan.tageson@xxxxxxxxxxx
-------------------- Internet e-Mail Disclaimer --------------------
This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you are not the intended recipient you are notified that any use,
disclosure, copying or distribution of the information is prohibited. In
such case, you should destroy this message and kindly notify the sender by
reply e-mail.The views expressed in this e-mail and any attachments are
personal and, unless stated explicitly, do not represent the views of
AddconIT. Furthermore, AddconIT will not be bound by this e-mail.
-----Original Message-----> bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
Sent: Monday, January 25, 2010 4:13 PM
To: Midrange Systems Technical Discussion
Subject: RE: Resetting QABNORMSW System Value
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.
As an Amazon Associate we earn from qualifying purchases.
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.