And be careful to prevent the loop detector from detecting itself (assuming you have debugged it perfectly), as it may have to run a long time in trying to detect a loop in 1000 other address spaces with 10000 tasks each without doing any I/O operations until the very end, when it reports that no loops were detected.
Bill Fairchild Rocket Software -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Shmuel Metz (Seymour J.) Sent: Friday, November 12, 2010 7:50 AM To: IBM-MAIN@bama.ua.edu Subject: Re: loop detection by program In <124554529.1289564475547.javamail.ngm...@webmail16.arcor-online.net>, on 11/12/2010 at 01:21 PM, Monika Amiss <monika.am...@arcor.de> said: > I want to examine all Asids every 3 minutes and > - if one Address Space appears to be looping - I > want to issued a Message to the operator. Be careful what you ask for - you might get it. Expect operators to cancel long running jobs "because they were looping." It's easy to detect that a job is looping, but it's impossible to automatically distinguish an erroneous loop from a valid loop, and every job more complicated than IEFBR14 does loop. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see <http://patriot.net/~shmuel/resume/brief.html> We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
