Greg Stigers said...
"Might this be a case of a job that one might want to run PRI=CS..."

Good idea, I just made the change.

And then asks...
"what are others leaving up during backup..."
         
#J1     EXEC        10S ZZ    SYSTEMQ  FRI  9:37P  NP92JOB,MGR.MINISOFT

#J3     EXEC        10S ZZ    SYSTEMQ  FRI  9:37P  JINETD,MANAGER.SYS

#J4     EXEC        10S ZZ    SYSTEMQ  FRI  9:37P  JSYSLOGD,MGR.SYSLOG

#J6     EXEC        10S ZZ    SYSTEMQ  FRI  9:37P  LOGOFF,MANAGER.SYS

#J7     EXEC        10S ZZ    SYSTEMQ  FRI  9:37P  JDAEMON,SERVER.SENDMAIL


We are running BackPack with Autosync for our back up software, so we are
able
to leave a lot running.  We do abort jobs that allow data access before we
start
such as:
        
#J1672  EXEC        10S ZZ    HPSYSJQ  THU 12:10A  QWEBS,MGR.QWEBS       
#J1676  EXEC        10S ZZ    HPSYSJQ  THU 12:10A  MSJOB,MGR.MINISOFT 

We set the user limit to zero before all this starts so we can leave JINETD
running.
The different job queues so the operator knows what can be left running. 
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *