Never ending Job and Subsystem
We have a job within a subsystem that just won't go away.
We have tried ending both the job and the subsystem it is running in but it never ends. This job has no program stack but does have open files and active object locks.
Is there anyway to end both the job and subsystem without having to power down the system (we’ve tried just putting it in a restricted state but there is no change)? Thank you
Software/Hardware used:
V5r4
We have tried ending both the job and the subsystem it is running in but it never ends. This job has no program stack but does have open files and active object locks.
Is there anyway to end both the job and subsystem without having to power down the system (we’ve tried just putting it in a restricted state but there is no change)? Thank you
Software/Hardware used:
V5r4
ASKED:
September 7, 2010 8:54 PM
UPDATED:
September 8, 2010 12:43 PM
Answer Wiki:
Carefully read the documentation for the <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/cl/endjobabn.htm">End Job Abnormal (ENDJOBABN)</a> command. Other than a forced PWRDWNSYS, I don't know of any way to end such a job.
Ending the subsystem won't help. The ending of a subsystem is always delayed until all jobs running in it have ended.
ENDJOBABN isn't an especially terrible or dramatic thing to do, but you should be prepared to recognize the things that come after it. The "abnormal IPL", for example, might cause your standard startup program to work differently. If you have PTFs that are waiting for an IPL, they will probably wait until the subsequent IPL.
Just read and be clear on the documentation. If you're comfortable with what it describes, then go ahead with it. If not, then post back here for more discussion.
Tom
To see all answers submitted to the Answer Wiki: View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
