Re: Will the next IPL be an abnormal IPL?

["bryan dietz" <bdietz400@xxxxxxxxx>]

You can scan the history log for the following message:
CPC1124    ENDJOBABN issued against job &3/&2/&1 by user &4.

http://www-1.ibm.com/support/docview.wss?rs=0&context=SWG60&dc=DB520&dc=D900&dc=D800&dc=DA900&dc=DA800&q1=ENDJOBABN+AND+AS400KBXXYYZZRCH&uid=nas16426d1c13107b12986256fa300577be7&loc=en_US&cs=UTF-8&lang=all
 -and-
http://www-1.ibm.com/support/docview.wss?rs=0&context=SWG60&dc=DB520&dc=D900&dc=D800&dc=DA900&dc=DA800&q1=ENDJOBABN+AND+AS400KBXXYYZZRCH&uid=nas1ce96ee887dd2f461862565c2007d2e84&loc=en_US&cs=UTF-8&lang=all

Bryan

On Thu, Apr 10, 2008 at 11:31 AM, <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
> --
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
> --
> 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.