Checking the ENDJOBABN Flag Setting

The most frequent cause for the CPF0998 - Unattended IPL in progress after abnormal system end message to be posted is because a job has ended abnormally. Many also result in a failure of the previous PWRDWNSYS to complete, resulting in an SRCB9003F10. The user can do a DSPOBJD on the ENDJOBABN command taking the *FULL DETAIL option and checking the date last used. This might have occurred some time ago indicating the ENDJOBABN was done under the covers by the system.

If a customer is getting this problem repeatedly (for example, on most IPLs), you might want to find which job is being ended abnormally. Normally, when the system ends a job abnormally, it immediately posts the CPF1164 job ending message with an ending code of 80 or 90. However, this may not occur because of an error in the job. In this case, the CPF1164 should be posted during the following IPL; for example, the message is posted for jobs that are not ended prior to a PWRDWNSYS timing out and forcing an SRCB9003F10 failure.

The system control block can be checked to determine if the ENDJOBABN has been used. This can be done interactively using the service tools or later by periodically dumping the object using the DMPSYSOBJ command by a CL program running off the job scheduler and then examining the outputs to be able to bracket the time period that the bit was set.

To dump the object using a command, on the OS/400 command line type the following:

DMPSYSOBJ OBJ(QWMSYSCB) CONTEXT(QSYS) TYPE(19) SUBTYPE(D3)

Display the resulting spool file and look at the first digit of byte 72 in the object's "SPACE-" section. This is the fifth (5th) digit of the fifth (5th) set of 8 digits on line 000060. If the digit is even, the bit is not set. If the digit is odd, the bit has been set indicating that the ENDJOBABN command was used. The even digits are 0,2,4,6,8,A,C,E. The odd digits are 1,3,5,7,9,B,D,F.

When examining QWMSYSCB using the service tools, use the MI object Option 25 for space (19) and the option to find by name and context. In this case, do a page down (to skip over the 100-byte header), and look at the first digit of byte 172.

You may find evidence of ENDJOBABN, via the following SQL statement run in ACS Run SQL Scripts:

SELECT MESSAGE_ID,
       MESSAGE_TYPE AS MESSAGE_TYPE,
       SEVERITY,
       MESSAGE_TIMESTAMP AS TIMESTAMP,
       FROM_USER,
       FROM_JOB,
       MESSAGE_TEXT,
       MESSAGE_SECOND_LEVEL_TEXT
    FROM TABLE (
            QSYS2.HISTORY_LOG_INFO(CURRENT TIMESTAMP - 3 DAY)
        ) x
    WHERE    MESSAGE_ID = 'CPI091D'  -- Previous ending abnormal, reason code &1. 
          OR MESSAGE_ID = 'CPI0990'  -- Previous ending was abnormal because ENDJOBABN used.
          OR MESSAGE_ID = 'CPC1124'  -- ENDJOBABN issued against job &3/&2/&1 by user &4.
          OR MESSAGE_ID = 'CPF0997'  -- Attended IPL after abnormal system ending.
          OR MESSAGE_ID = 'CPF0998'  -- Unattended IPL in progress after abnormal system end.   
;