My experiences differ. I log when we do an ENDJOBABN. And that lpar
always requires a second IPL to apply OTHER than the MF* ptfs in 5761999.
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/cl/endjobabn.htm?resultof=%22%65%6e%64%6a%6f%62%61%62%6e%22%20
Use of the ENDJOBABN command causes the next system end to be marked as
ABNORMAL. Certain system functions are then called during the subsequent
IPL to clear up conditions that may have resulted from running the
ENDJOBABN command. This does not, however, cause any machine recovery
functions to be called, nor do any access paths need to be rebuilt. Some
storage in use by the job may become unavailable after the ENDJOBABN
command is run and that available storage can be reclaimed by using the
Reclaim Storage (RCLSTG) command.
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/rzal2/rzal2abnormalipl.htm?resultof=%22%65%6e%64%6a%6f%62%61%62%6e%22%20
Causes of abnormal IPLs
These situations can cause an abnormal initial program load (IPL).
Using the End Job Abnormal (ENDJOBABN) command. To see if this command has
been used, look for message CPC1124 in the job log.
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/rzam8/rzam8fixinstallverify.htm
Normal PTF processing occurs only during an unattended IPL (initial
program load) that immediately follows a normal system end.
If you did not specify Y for Perform Automatic IPL on the Install Options
for PTFs display, verify that the Power Down System (PWRDWNSYS) command
was run with RESTART(*YES) and that the key lock position was at normal.
If an abnormal IPL occurs, some Licensed Internal Code fixes might be
installed, but no other operating system or licensed program PTFs are
applied. You can look at the previous end of system status system value
(QABNORMSW) to view whether the previous end of system was normal or
abnormal.
DSPMSGD CPI091D, reason code 1.
DSPMSGD CPC1124
Try this before your next IPL (or 1 day short of the interval in GO
CLEANUP, 1. Change cleanup options, Number of days to keep System journals
and system logs):
DSPLOG PERIOD((*AVAIL *BEGIN)) MSGID(CPC1124)
There was an enhancement several releases ago to at least apply "most" of
the 57##999 ptf's during the first IPL of an abnormal IPL. This did not
get expanded out to OS or LPP.
This is why my instructions after an IPL to apply a ptf have the operator
record the value for QABNORMSW, check WRKPTFGRP for abnormalities, check
DSPPTF 5761SS1 and more.
Rob Berendt
midrange.com
