If a cancel appears not to be working one thing I would do is reset the job being canceled into a high resource service class. Sometimes tasks that appear to be hung are instead slow.
On Wed, Dec 3, 2008 at 2:58 PM, rdeguz1 <[EMAIL PROTECTED]> wrote: > Anyone got burned by issuing the Force command (without ARM) and had to > re-ipl? > > I myself have had issued FORCE without ARM to terminate a rogue batch job > that just wont budge using repeated CANCEL and KILL. I've been fortunate > that night to not have had to re-IPL our system. > > > > z/OS 1.9 FORCE COMMAND WARNING > "Consider using the FORCE command as a last resort when the CANCEL > command still fails to perform its function after you have issued it > several > times." > > Gone is the other warning that states: (circa 1996) > Never use the FORCE command without understanding that - After issuing > FORCE, you might have to re-IPL." << something to that effect. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > -- Glen J. Gasior (630) 712-2104 Chicago, Illinois 60611 "Leadership that improves the process of change" ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
