We have an older ISV system that has DEEP hooks into the OS. Two years ago, when it ran its fiscal year calendar update, it had a problem and started chunking out messages and preventing jobs from starting. Operator panic lead to a bypass of normal procedure, a cancel and then a force. We had to 'drag and drop' IPL out of that one. That was a fun oh:dark:30 call. Recreated that problem in the testbed. Cancel, force (with or without arm) required an IPL every time. Funny thing - the standard P command shut the application down every time and it cleaned up after itself, no harm, no foul.
IMHO - I save the force for times when the problem is so serious that the problem would cause us to IPL if we can't fix it. When we do use it, it generally works fine. In my testbed, prior to moving a product to production, I alway negagtive test, including clobbering the product on purpose. It's good to get an idea of what might happen... Linda Mooney -------------- Original message -------------- From: William Bishop <[EMAIL PROTECTED]> > Got burned because someone setup automation to escalate a P TCAS to a > FORCE TCAS if it didn't come down in a timely fashion. > > Operations inadvertenly issued a P TCAS during the day and didn't respond > to FSTOP. > > Automation eventually did a FORCE TCAS. > > Ended up IPL'ing to clean that up. > > Then had the Operations Analyst responsible for Automation get into an > argument with me when I said you can't do that. His rational was because > that was the way he was told to escalate things. > > Thanks > > Bill Bishop > > Specialist > Mainframe Support Group > Server Development & Support > Toyota Motor Engineering & Manufacturing North America, Inc. > [EMAIL PROTECTED] > (502) 570-6143 > > > > rdeguz1 > Sent by: IBM Mainframe Discussion List > 12/03/2008 04:10 PM > Please respond to > IBM Mainframe Discussion List > > > To > IBM-MAIN@bama.ua.edu > cc > > Subject > Got burned by the FORCE COMMAND ? > > > > > > > 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 > > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
