×
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.
Is there a way to tell if anyone ran an ENDJOBABN, or any such thing that
will make the next IPL be an abnormal IPL?
Situation:
Scheduled downtime. Do save and stuff. Perform IPL. Check PTF's to see
if they applied. If they didn't then check system value QABNORMSW. If
that is 1, then follow steps to bring the system down in an orderly
fashion, do the endsbs, and IPL again.
QABNORMSW is only set at the IPL. We can't check it before the first IPL
and get anything meaningful. Repeat, if you do a ENDJOBABN and then check
QABNORMSW that didn't change it. Only the IPL after the ENDJOBABN changes
it.
What I'd like to do is:
Check to see if an ENDJOBABN was run.
If so then CHGIPLA STRPRTWTR(*NO) STRRSTD(*YES)
Then IPL twice. The STRRSTD will cut a significant amount of time and
effort to bring the system back into a restricted state after the first
IPL.
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.
midrange.com
