Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
Identifying a looping job is usually done by looking at the way the job is performing using S.DA or some monitor product. If the job is using a lot of cpu cycles and is doing no i/o, it may well be in a loop.
If you have a job that does all of the work it needs to do, and then starts over and does everything over and over again, that will be more difficult to detect. It will not appear to be in a loop as it will be doing i/o and using cpu time.
Depending on how your system is configured, the job may eventually time-out for one reason or another or it may be canceled.
If i've misunderstood your question, please advise.