Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!gatech!bloom-beacon!think!ames!ucbcad!ucbvax!SPCA.BBN.COM!gwalker From: gwalker@SPCA.BBN.COM (Gail Rubin Walker) Newsgroups: comp.os.vms Subject: Re: DCL programming and BACKUP journaling question Message-ID: <8707240040.AA05582@ucbvax.Berkeley.EDU> Date: Thu, 23-Jul-87 16:28:39 EDT Article-I.D.: ucbvax.8707240040.AA05582 Posted: Thu Jul 23 16:28:39 1987 Date-Received: Sat, 25-Jul-87 10:49:20 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 14 The answer to your problem with DCL and OPEN is by default, OPEN only opens a file for READ. This is not related to file protection; the term "file access" relates to how you opened the file. See HELP OPEN for all the info you need on the various switches to OPEN; at a minimum you need to use the /WRITE switch. I don't have any real clues to your problem with the BACKUP journal files; I haven't seen the problem myself though I'm not doing system management these days. Is there more info you could provide? What command are you using to list the BACKUP journal file? Does ANALYZE/RMS on the journal file give you any information that may point to the problem? Does this happen immediately after the journal file is created, or at some later time? -- Gail Walker