Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!mit-eddie!genrad!decvax!ucbvax!XEROX.COM!"Peter_A._Hwang.WBST147" From: "Peter_A._Hwang.WBST147"@XEROX.COM Newsgroups: comp.os.vms Subject: DCL programming and BACKUP journaling question Message-ID: <870723-090735-1955@Xerox> Date: Thu, 23-Jul-87 12:04:58 EDT Article-I.D.: Xerox.870723-090735-1955 Posted: Thu Jul 23 12:04:58 1987 Date-Received: Sat, 25-Jul-87 08:41:33 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 40 Greetings to netlanders: While implementing a comprehensive BACKUP system, I have some questions that I hope someone on the network has answers: 1. DCL write/update does not work for me. For a test case I created a file called j.1 which has two records: 22-JUL-1987 23-JUL-1987 I then open the file with: $ open/share io j.1 Read the records: $ read io rec1 $ read io rec2 Update rec2 with rec1: $ write/update io rec1 At this point I got the error message: %RMS-F-FAC, record operation not permitted by specified file access (FAC). The file is owned by me and the protection code is O:RWED. It is a sequential file. This code is tested under VMS 4.5. 2. BACKUP journaling file corrupts easily Over the last month alone I experienced several corrupt backup journal files during daily and weekly incremental backup operations. The corruption is detected only when I tried to list the journal file. The typical error messages are: %BACKUP-F-INVBJLSIZ, invalid record size in BACKUP journal %BACKUP-F-INVBJLTYP, invalid record type in BACKUP journal What is the cause of the invalid size or invalid record type ? Is there any way to avoid them ? Any easy way to reconstruct the journaling file ? Many thanks in advance. Peter Hwang Xerox Corp.