AUTOBRU.CMD IS AN MCR COMMAND FILE TO AID IN PERFORMING OUR WEEKLY SYSTEM MAINTAINENCE. IT PERFORMS ANY OR ALL OF THE FOLLOWING TASKS. 1. DELETE ALL LIST AND MAP FILES 2. PURGE ALL DIRECTORIES 3. TRUNCATE ALL FILES 4. VERIFY THE DISK FOR LOST FILES 5. RUN ERROR LOG 6. SAVE THE SYSTEM DISK TO TAPE WITH BRU A. FULL OR INCREMENTAL SAVE B. MOUNTED OR UNMOUNTED C. APPEND TO END OR START NEW TAPE 7. LOGOUT. - ONLY IF SAVE NOT PERFORMED EACH OF THESE ARE INDIVIDUALLY SELECTED AND THEN PERFORMED. THE FIRST THREE ARE TO RECOVER UNNEEDED BLOCKS FROM THE DISK. THE NEXT TWO VERIFY THE SYSTEM IS OPERATING PROPERLY AND THE 6TH IS TO SAVE THE SYSTEM DISK ON TAPE. IF AN INCREMENTAL SAVE IS TO BE PERFORMED, TRUNCATE SHOULD NOT BE PERFORMED AS IT WILL CHANGE THE REVISION DATES OF ALL FILES. IF THE SAVE IS PERFORMED IT WILL BE GIVEN THE BACKUP SET NAME DDMMM WHERE DD AND MMM ARE THE CURRENT SYSTEM DATE. ALSO IF AN INCREMENTAL SAVE IS TO BE PERFORMED, THE DATE OF REVISION WILL BE TAKEN FROM THE FILE BRUDATE.DAT. THE CURRENT DATE AND TIME WILL ALSO BE STORED IN BRUDATE.DAT TO PREPARE FOR THE NEXT INCREMENTAL SAVE. A RECORD OF ALL SAVES IS KEPT BY APPENDING THE LATEST BRU COMMAND FILE (BR.CMD) TO THE HISTORY FILE BRU.HIS. IN PREPARING THIS FILE I AM ASSUMING IT WILL BE USED BY EXPERIENCED PROGRAMMERS FAMILIAR WITH INDIRECT COMMAND FILES AND WITH BRU. THIS COMMAND FILE IS SET UP TO WORK WITH DEVICES DR: AND MM:. IT SHOULD BE SIMPLE TO CHANGE THESE. ALSO OUR SYSTEM USES VIRTUAL DISKS (FROM PREVIOUS DECUS SYMPOSIA TAPES). THESE ARE CHECKED AND DISMOUNTED FOR AN UNMOUNTED SAVE. IF YOUR SYSTEM DOESN'T HAVE THEM, COMMAND LINES REFERENCING VD: SHOULD BE DELETED. TO PREPARE THE HISTORY AND DATE FILES, THE FILE ABBLD.CMD HAS BEEN INCLUDED AND SHOULD BE RUN BEFORE USING AUTOBRU. GOOD LUCK, PLEASE LET ME KNOW IF YOU HAVE ANY COMMENTS CRITICISMS OR SUGGESTIONS. FRANK HALLAHAN FORD AREOSPACE & COMMUNICATIONS CORP 3939 FABIAN WAY MS-X90 PALO ALTO, CA 94303 PHONE: (415) 494-7400 EXT 5015