Hallo,
ich habe zu dem endjobabn noch folgendes:

ENDJOBABN has been known to take down jobs that are too stubborn for ENDJOB. But it has a few limitations that you need to be aware of. Specifically, the following things affect ENDJOBABN use:
ENDJOBABN cannot be run against a job before you've attempted to end the job through the ENDJOB command, with *IMMED specified in the "how to end" parameter. OS/400 is also hard-coded to ignore an ENDJOBABN statement until 10 minutes have passed since you ran an ENDJOB *IMMED command on the same job. So not only do you have to run ENDJOB for a problem job before using ENDJOBABN, you also have to give ENDJOB time to work.

ENDJOBABN is shipped with *PUBLIC *EXCLUDE authority. And to run ENDJOBABN, you need job control (*JOBCTL) authority in your user profile.

ENDJOBABN can be run against a job only once. Additional ENDJOBABN commands can't be run.
So if you keep these restrictions in mind, ENDJOBABN can be a powerful addition to your OS/400 system administrator toolkit, and be the thing you reach for when you can't end a job any other way.