Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!columbia!rutgers!ucla-cs!zen!ucbvax!XEROX.COM!"Peter_A._Hwang.WBST147" From: "Peter_A._Hwang.WBST147"@XEROX.COM Newsgroups: comp.os.vms Subject: Partial answer to my question of Jul 23 Message-ID: <870724-074825-2420@Xerox> Date: Fri, 24-Jul-87 10:48:07 EDT Article-I.D.: Xerox.870724-074825-2420 Posted: Fri Jul 24 10:48:07 1987 Date-Received: Sat, 25-Jul-87 14:43:19 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 24 Some distinguished persons correctly solve my write/update problem. The file should be opened with /read/write/share qualifiers. Thank you for these nice people. Question #2 still needs answer. --- 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 record 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. ---