Rory, what I do as a failsafe for the situation that you described is
this;
put a parameter in the !job card either called 'time' or 'cpu', I think
its
time=xxxx.
calculate the maximum cpu seconds that the job might use under the worst
conditions, then quadruple it..  if your job gets into the 'loop of death'
again
eventually, it will commit suicide when the maximum cpu seconds run out.
also, to avoid the 'box of paper of death' when you stdlist starts
printing..
include a lp,1,1 in your outfile settings..this way, your stdlist will
stay in the spooler for analysis in case of trouble.
Jim Sanders, MTX Corp