Re: Abnormal system end

> 1. Unattended IPL in progress after abnormal system end
> 2. Previous ending was abnormal because ENDJOBABN used.

> After further investigation I noticed the system had taken an extra 2h
> 20mins to IPL on Saturday morning after the backup procedure, due to the
> abnormal end I assume.

> I know I did not issue the ENDJOBABN command during any of the procedure
(I
> have checked the logs, splf's, etc. to confirm). Possibly it had been
issued
> earlier in the week on a runaway user job, if so does using the ENDJOBABN
> command allways result in the above ?
> Does the ENDJOBABN command have any affect on the QABNORMSW system value
?


ENDJOBABN command can be issued only 10 mins after ENDJOB *IMMED was issued
for a job and this job is still around.
Due to the nature of this command, job being ended will not be properly
cleaned up.
Therefore it raises a flag, so that system considers next system end as
abnormal and performs more than usual checking at next IPL.

QABNORMSW system value is a place, where user program may check
success/failure of last IPL without going thrugh history logs, QSYSOPR
message queue etc.
Of course, system end, flagged as abnormal by ENDJOBABN, will be reflected
in QABNORMSW.


Alexei Pytel


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---