-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Not an answer, but for general info, I had to run an endjobabn last year
(V5R4) and was surprised to find that the system IPL'd normally.
Apparently endjobabn no longer automatically forces a manual IPL.
Pete Hall
pbhall@xxxxxxxxxxxxx
Bruce Vining wrote:
| I don't have access to a system right now, but when an ENDJOBABN is
run a specific message (which one I can't remember and without a
system...) is sent to QHST. You could scan (or watch for) this message
in QHST.
|
| Bruce
|
| rob@xxxxxxxxx wrote:
| 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
http://enigmail.mozdev.org
iD8DBQFH/rVspcZsDl8OX6kRAtRUAJ0UEmK7kv06bgr5eaTECydWFuhQVACaAiP9
XuGthViGS/bgOL+idbJ/xDw=
=PmWg
-----END PGP SIGNATURE-----
midrange.com
