JCV@CERNVM.BITNET.UUCP (02/20/87)
About a week ago, we had to restore a disk from a set of backups because of a head crash. After restoring the total backup, a number of incremental backups were applied, all generated with /SINCE=BACKUP. That worked fine; however, no new ACCOUNTNG.DAT was restored. The reason being that it wasn't backuped - its modification date is never updated by the job controller. To avoid this problem in the future, our backup command procedure now does a SET PROT=W on ACCOUNTNG.DAT before it produces an incremental save set. This will change the modification date and will force the file to be backed up. This should work for all files which are permanently open but modified, like disk-mapped global sections ($UPDSEC doesn't change the modification date). --- Jan Vorbrueggen P.S. Of course the /IGNORE=INTERLOCK qualifier has to be used on the backup command. The file should be ok, however, as a $FLUSH is done after every write to guarantee the file contents are up to date. Same as above goes of course for JBCSYSQUE.DAT and the PSI accounting file.