🚀 go-pugleaf

Message-ID: <3FB827F0.6457B6DF@istop.com>
From: JF Mezei <jfmezei.spamnot@istop.com>
X-Mailer: Mozilla 4.76 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.vms
Subject: Re: DCL Enhancements: Error messages for OPEN and DEFINE
References: <b096a4ee.0311161730.92cca90@posting.google.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Forwarded: by - (DeleGate/8.5.4)
Lines: 12
Date: Sun, 16 Nov 2003 20:44:36 -0500
NNTP-Posting-Host: 64.230.46.34
X-Complaints-To: abuse@sympatico.ca
X-Trace: news20.bellglobal.com 1069033349 64.230.46.34 (Sun, 16 Nov 2003
20:42:29 EST)
NNTP-Posting-Date: Sun, 16 Nov 2003 20:42:29 EST
Organization: Bell Sympatico

"Alan E. Feldman" wrote:
> $ OPEN FOO FILE.TMP
> $ OPEN FOO OTHER.TMP
> 
> I'd like to see an error message for this saying that FOO is already
> pointing to FILE.TMP.

This might break existing procedures though. (unless the error message is a
success message which means that no "ON ERROR/WARNING" would be triggered.)

Another option would be to add some qualifier for OPEN to request such a
message if the file is already opened.

               ----------

Message-ID: <3FB801BB.815B62DC@wilderness.org>
From: Furry Raccoon <F.Racoon@wilderness.org>
X-Mailer: Mozilla 4.76 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.vms
Subject: Re: Backups and shadowed system disk
References: <1dafe751.0311121151.115b54f2@posting.google.com>
<3fb29367$0$13304$626a54ce@news.free.fr>
<5pxsb.8911$XD6.1344@news.cpqcorp.net>
<8a646952.0311140858.4ba3b6a6@posting.google.com>
<3fb521e8$0$27041$626a54ce@news.free.fr>
<8a646952.0311141430.4bfc871d@posting.google.com>
<bp8tv8$1jemb1$2@ID-120847.news.uni-berlin.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Forwarded: by - (DeleGate/8.5.4)
Lines: 18
Date: Sun, 16 Nov 2003 18:01:24 -0500
NNTP-Posting-Host: 64.230.46.34
X-Complaints-To: abuse@sympatico.ca
X-Trace: news20.bellglobal.com 1069023569 64.230.46.34 (Sun, 16 Nov 2003
17:59:29 EST)
NNTP-Posting-Date: Sun, 16 Nov 2003 17:59:29 EST
Organization: Bell Sympatico

John Travell wrote:
> However much you are able to move off the system disk, the one file that you
> CANNOT move that WILL be written to by the OS under certain circumstances is
> SYS$BASE_IMAGE.

At what frequency is that file updated ? Does that file have some form of
an
index, or is it simply the matter of updating a specific disk block ?

What information is contained in the dynamic information stored in that
base$image ? Can this cause a system to fail to boot, or is the worst that
can
happen is the system, upon booting, doesn't see some bit indicating a
proper
shutdown and then proceeds to do mount verification/rebuild of the system
disk ?

> It is NOT POSSIBLE to create (with released software) a VMS system disk that
> will NEVER be written to.

How do they handle Alphas to boot VMS from CD ?  Or is that really just a
glorified standalone backup system that isn't called "standalone backup" ?