Some years ago, in pursuit of Headcount reduction, a decision was made to suppress the display of WTORs that weren't recognized by automation (OPS/MVS) as important. This had the desired effect, and headcount reduction proceeded. In the years since then, the remaining operators have learned to do the displays and check for unanswered WTORs. But this happens on a very intermittent basis.
So, on July 28, a batch job was giving trouble, and one of the operators entered: F R,R,EXIT=xxxxxxxx (This will cause MAINVIEW to terminate the address space) Which promptly generated a WTOR which was not seen because of the rule described in the first paragraph above. The job was later removed via the MVS FORCE command. Fast forward from July 28 to September 11 (a date filled with premonitions of doom.) An operator does the appropriate display and notices the WTOR. Asks the MVS oncall person how to deal with it, and gets a response to reply 'U'. Oops. This caused MAINVIEW to issue a couple of messages that it had terminated job xxxxxxxx. Followed immediately by MVS and JES3 issuing messages that an IMS DBRC address space had just gone away in the ugliest possible manner. In all the fun and games that follow such an interesting event, it seems never to have occurred that there might be a correlation between the smoking gun in their hand, and the hole in their foot. Most curious. ---------------------------------------------------------------------- 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
