OK, so that's not COMPLETELY unresponsive, because you are gettingloop.
some I/O. That's a clue, not a nit. Look at the actual machine. Are
the disk drive activity lights very busy? If yes, you may have a
runaway query. If no, you may have a runaway CPU hog in a very tight
Also, check to see if you have an SRC.
If you can afford to wait, see if you can get to a command line and
change your job priority to 2 and then WRKACTJOB, WRKSYSSTS to see
what's going on in there. If you can't afford to wait, force an IPL
and look at QHST to see if there's a clue as to what happened.
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact