CPF1164: Job ended

What it means

CPF1164 is written at the end of every job's log and to the history log, QHST. It names the job (number/user/name), the date and time it ended, the processing time used, and an end code. The end code is the part that matters. IBM defines these values.

• 0. The job completed normally.
• 10. Completed normally during a controlled end of the job or its subsystem.
• 20. The job exceeded its end severity (the ENDSEV job attribute).
• 30. The job ended abnormally.
• 40. The job ended before it became active.
• 50. The job ended while it was active.
• 60. The subsystem ended abnormally while the job was active.
• 70. The system ended abnormally while the job was active.
• 80. The job was ended with ENDJOBABN.
• 90. The job was forced to end after the ENDJOBABN time limit.

After an abnormal system end, the system may not manage to log CPF1164 at the time. IBM notes that it is then posted during the next IPL.

Common causes

• Every job that ends logs CPF1164, including sign-offs, so on its own it isn't an error.
• End code 20 or 30 usually means a program hit an error nothing handled, such as a function check, and the job ended.
• End code 50 often means the job was ended from outside while running, for example with ENDJOB.
• End codes 60 and 70 mean the subsystem or the whole system went down underneath the job.
• End codes 80 and 90 come from ENDJOBABN, used when a job won't end normally.

How to find the problem

1. Look at the last message of the job log, from DSPJOBLOG or the QPJOBLOG spooled file (WRKJOB option 4). Press F1 on CPF1164 to read the end code.
2. Search QHST with DSPLOG LOG(QHST) MSGID(CPF1164), adding a date range or JOB(name) to narrow it.
3. For a non-zero end code, read the job log upwards from CPF1164. The first escape or CPF9999 function check is usually the cause.
4. For the submitter's view, check the user's message queue with DSPMSG for CPF1241 (completed normally) or CPF1240 (ended abnormally).

How to fix it

• For end code 0 or 10, nothing is wrong.
• For 20 or 30, fix the error shown earlier in the job log, then rerun the job.
• For 50, find out who or what ended the job. The job log and QHST usually record the end request and the user who made it.
• For 60 or 70, investigate the subsystem or system failure first, then rerun affected jobs.
• If job logs come out too short to help, raise the logging level. Use CHGJOB LOG(4 00 *SECLVL) for a running job, or CHGJOBD with the same LOG value on the job description so future jobs get it.

DSPMSGD MSGID(CPF1164) MSGF(QSYS/QCPFMSG)

Technical reviewer: Albert Joseph, WND Software.

Last reviewed 2026-10-18 by the WND Software team. Written in our own words. For the full reference, check IBM’s documentation for your IBM i release.