Stubborn iSeries Jobs
Read Time:1 Min, 28 Sec
I am not an iSeries expert…
However, since we use the iSeries for our E1 Enterprise Server I am required to use it more than I ever wanted to. Anyway, I have been doing some experimenting with the XML Kernel jobs that get started up, when one of the kernel jobs did not end when I issued the endnet command. So, I used wrkactjob and issued an endjob command with *IMMED. Well, after waiting a while it didn’t end. After about 30 minutes of trying other things and talking to our resident iSeries guru, I gave up and left for the day.
I got in this morning to find the jobs still “ending”. So, I did some looking through Google and found another command that I could try ENDJOBABN (End Job Abnormal).
Info from an article on ITJungle.com:
ENDJOBABN JOB(999999/USER/JOBNAME)
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.
Happy
0
Sad
0
Excited
0
Sleepy
0
Angry
0
Surprise
0
Average Rating