Nicholas Mickey wrote in message ... >hi, > >I ran into a problem, when I tried to abort a backup >job. The stdlist is telling me that its releasing >the locked files, but its been in the que for about 12 >hours. Is there another way I can abort this job >without using the abortjob(already tried) command ... First, do a 'RECALL' and see if there is a pending reply for the backup LDEV. If so, 'REPLY' with either a '0' if an LDEV# is expected or "NO" if "YES/NO" is expected. If that's not the problem, then try doing 1 or more ABORTIO commands -- using the backup device LDEV#. The backup program could be waiting for an I/O to complete on the tape; and if it's not mounted, then this may get the backup program to a point where it will terminate. The RR main process has seen the 'ABORTJOB' request -- since it has released the files, but the tape I/O process is probably blocked for one of the above reasons and doesn't know an ABORTJOB is pending. A 'SHOWPROC' on the JOB might also be useful if the above suggestions don't help (RR actually runs as multiple processes ('heavyweight' threads), so check each one for process state. Winston K.