6 Aug
2002
6 Aug
'02
1:05 p.m.
VMS has a distinctive that when you open a file for write or append, a copy
of that file is made with a higher "Version" number.
What happens then if you have a "log" type file, the OS (or some application)
open it from time to time to add info.
Mass copies of this file?
6 Aug
6 Aug
1:30 p.m.
VMS does keep versions of log files, but you can set the OS up to only
keep a specified number of versions on a file by file basis or more
globally.
You can also manually purge older versions of a file or a set of files
keeping a specified number of versions.
Erik
-----Original Message-----
From: cctalk-admin(a)classiccmp.org [mailto:cctalk-admin@classiccmp.org]
On Behalf Of Ron Hudson
Sent: Tuesday, August 06, 2002 3:04 PM
To: Classic Computers
Subject: VMS question
VMS has a distinctive that when you open a file for write or append, a
copy
of that file is made with a higher "Version" number.
What happens then if you have a "log" type file, the OS (or some
application)
open it from time to time to add info.
Mass copies of this file?
1:56 p.m.
VMS has a distinctive that when you open a file for
write or append, a copy
of that file is made with a higher "Version" number.
What happens then if you have a "log" type file, the OS (or some application)
open it from time to time to add info.
Mass copies of this file?
You can open, update, and close an existing file without
creating a new version, if that's what you want.
--
Eric Dittman
dittman(a)dittman.net
Check out the DEC Enthusiasts Club at http://www.dittman.net/
7 Aug
7 Aug
12:20 a.m.
In fact, opening a file in "append" mode will not create a new version,
but add information to the *end* of the existing file without moving
existing data around, as with any other operating system. This would be
the right way to update a .LOG file.
Opening a file for "write" access will also use the existing file, but
will leave you positioned at the *start* of the file. For sequential
files (as opposed to index-sequential), this will result in the existing
file getting truncated to zero length, and contents replaced with what
the program writes from the beginning.
If you "create" a file, however, the old version will stay in place, and
a new file (with the next higher version number) will be started. That's
what most standard utilities do to output their results, e.g., that's
what a VMS editor will do when you EXIT.
Andreas
Eric Dittman wrote:
--
Andreas Freiherr
Vishay Semiconductor GmbH, Heilbronn, Germany
http://www.vishay.com
VMS has a distinctive that when you open a file
for write or append, a copy
of that file is made with a higher "Version" number.
What happens then if you have a "log" type file, the OS (or some application)
open it from time to time to add info.
Mass copies of this file?
You can open, update, and close an existing file without
creating a new version, if that's what you want.
--
Eric Dittman
dittman(a)dittman.net
Check out the DEC Enthusiasts Club at http://www.dittman.net/ 
6 Aug
6 Aug
8:47 p.m.
At 03:04 PM 6/08/2002 -0700, Ron Hudson wrote:
VMS has a distinctive that when you open a file for
write or append, a copy
of that file is made with a higher "Version" number.
What happens then if you have a "log" type file, the OS (or some application)
open it from time to time to add info.
Mass copies of this file?
You can open a file to append, in which case the version number isn't
changed. Of course, typical VMS applications open the log file and never
close it and assuming you code it correctly, other applications can read
the log file.
Huw Davies | e-mail: Huw.Davies(a)kerberos.davies.net.au
| "If God had wanted soccer played in the
| air, the sky would be painted green"
11:20 p.m.
You can open a file to append, in which case the
version number isn't
changed. Of course, typical VMS applications open the log file and never
close it and assuming you code it correctly, other applications can read
the log file.
Unfortuantly at least version 1.9 of Samba (yeah, I know it's ancient, but
it works for me) has the bad habit of creating a LOT of log files. I
finally ended up creating a batch job to clean up after it.
Zane
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh(a)aracnet.com (primary) | OpenVMS Enthusiast |
| | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| PDP-10 Emulation and Zane's Computer Museum. |
| http://www.aracnet.com/~healyzh/ |
7 Aug
7 Aug
3:21 a.m.
At 01:18 AM 7/08/2002 -0700, Zane H. Healy wrote:
Without appearing to have a go at the Samba team (they do a great job and I
use Samba
every day), it's a typical problem when Unix software is "ported" to VMS.
Basically
all that happens is enough changes are made to make something work without
making it
VMS friendly. Hopefully with some of the work that is currently going on in
HP to make
VMS have the same API as Solaris will make more applications available and
also work
more like their Unix counterparts.
Huw Davies | e-mail: Huw.Davies(a)kerberos.davies.net.au
| "If God had wanted soccer played in the
| air, the sky would be painted green"
You can open a
file to append, in which case the version number isn't
changed. Of course, typical VMS applications open the log file and never
close it and assuming you code it correctly, other applications can read
the log file.
Unfortuantly at least version 1.9 of Samba (yeah, I know it's ancient, but
it works for me) has the bad habit of creating a LOT of log files. I
finally ended up creating a batch job to clean up after it. 
6:46 a.m.
At 01:18 AM 8/7/02 -0700, you wrote:
Hey, I have an unused distribution of "rumba" which claims to
do what samba does but on VMS. Has anybody ever used it?
Is it any good?
carlos.
--------------------------------------------------------------
Carlos E. Murillo-Sanchez carlos_murillo(a)nospammers.ieee.org
You can open a
file to append, in which case the version number isn't
changed. Of course, typical VMS applications open the log file and never
close it and assuming you code it correctly, other applications can read
the log file.
Unfortuantly at least version 1.9 of Samba (yeah, I know it's ancient, but
it works for me) has the bad habit of creating a LOT of log files. I
finally ended up creating a batch job to clean up after it.
Zane
8092
days inactive
8093
days old
7 comments
7 participants
participants (7)
-
Andreas.Freiherr＠Vishay.com -
carlos_murillo＠epm.net.co -
classiccmp＠vintage-computer.com -
dittman＠dittman.net -
healyzh＠aracnet.com -
Huw.Davies＠kerberos.davies.net.au -
rhudson＠cnonline.net