|
From the helptext for CHGIPLA......Page down to the section on STRRSTD.
Vern,Jerry@xxxxxxxxxxxxxxx 02/20/2010 8:50:26 AM >>>
I hit Enter before I added that I still have no idea why the QABNORMSWvalue was '1' (abnormal). I did write a program to run daily that will
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
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
Sent: Monday, January 25, 2010 10:33 AMwill
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
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
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.