Re: "Undead" Jobs

Repeat after me: Never try ending a subsystem to kill a job. If you have
any doubt, repeat it. If ENDJOB will not kill it and (after you wait the
required ten minutes) ENDJOBABN will not kill it, then ENDSBS most
definitely will NOT end the job. The only think it will do is
1 - kill other jobs
2 - Put the subsystem in an ending state
3 - When you realize it won't work and you try STRSBS to allow other jobs
in the subsystem it will tell you NO WAY because it has to end all the way
first. Which, since the offending job will not end it cannot.

I tried ENDSBS QSPL to kill a writer job that wouldn't end. Of course, it
did no good in ending the job. All it did was not allow me to start any
writers until I IPLed the system. Could I have done without one stinking
writer versus IPLing the machine? Hell yes! All writers? No.

Many of you will not listen to me and will try the ENDSBS anyway. If so,
ask yourself this first. When this doesn't work can I do without this
subsystem until the next scheduled IPL, or, have I already cleared it with
the users to do an IPL now? That's the only time to make your bound to
fail attempt at using ENDSBS to try to end a job - when you have your IPL
scheduled already to get out of it. Better to come out smelling like a
rose because it didn't take the system down then to go to the next level
with less notice.

Rob Berendt