LD062 Install Question
Tom Linden
unzipped it
produces LD062.[A-K] but running VMSINSTALL only restores savesets A and E.
Is this
correct?
Dirk Munk
version. Depending on which version is found, the applicable LD savesets
are used. There is a LD063 by the way, this can be used for VMS 7.3.
Jan-Erik Söderholm
This should be clear from the "Installation Guide", btw...
Jan-Erik Söderholm.
Tom Linden
from David Dachtera's site seems to have some changes made as indicated in
the Readme, particularly in regards to the creation of the zip file. Has
this
been incorporated in 6.3?
BTW, Jan-Erik, there was no Installation Guide with the kit I downloaded.
> -----Original Message-----
> From: Dirk Munk [mailto:mu...@home.nl]
> Sent: Monday, March 18, 2002 9:23 AM
> To: Info...@Mvb.Saic.Com
> Subject: Re: LD062 Install Question
>
>
> Yes, that can be correct. The installation procedure checks for the VMS
> version. Depending on which version is found, the applicable LD savesets
> are used. There is a LD063 by the way, this can be used for VMS 7.3.
>
Jan-Erik Söderholm
I just noted that when an installation script doesn't
install all savesets, it's often due to that some are
for VAX and some are for Alpha.
Now, since you downloaded this from Davids site, maybe
asking him could give "Better Answers" :-)
Jan-Erik.
Dirk Munk
It consists out of a driver for the Logical Disks, and a utility to
create, connect etc. the disks.
It was developed by Jur van der Burg from Compaq in The Netherlands.
With the utility you can create a special file on a normal VMS disk.
This file is then 'connected' to the LD driver, and bingo you have a new
disk.
These disks are numbered LDA1, LDA2, and so on.
In theory you can create about 26000 LD disks (LDA1 to LDZ9999).
You can use such a disk vitualy the same as you would use a normal disk.
It is a very handy tool, for instance to get all VMS documentation CD's
on line on your system.
Create LD devices, backup the CD's to these devices, and that's it.
And since these 'disks' are files, you can copy or FTP complete disks to
another location.
Very handy indeed !
David J. Dachtera
>
> Are you recommending to use 6.3 instead of 6.2? The 6.2 kit I downloaded
> from David Dachtera's site seems to have some changes made as indicated in
> the Readme, particularly in regards to the creation of the zip file. Has
> this
> been incorporated in 6.3?
>
> BTW, Jan-Erik, there was no Installation Guide with the kit I downloaded.
I don't recall there ever being an install guide other than the release
notes in the .A saveset, but it's been a while.
My "changes" to LD V6.2 (LD062) were to remove the attempt by the
KITINSTAL.COM to "phone home" at install time. That's it.
I believe it also comes with source which would be in one or more of the
"extraneous" savesets.
I haven't look at LD V6.3 (LD063) yet. It'll be a while until I'm ready
put up V7.3 here at the home office. I still plan to play with
PostScript viewing and, as I recall, V7.3 removes "Display PostScript"
support in DECwindows, even if you have an older DECwindows installed
(V1.2-4 or earlier).
I don't yet know if the KITINSTAL.COM for V6.3 still has the "phone
home" "feature" (bug?).
--
David J. Dachtera
dba DJE Systems
http://www.djesys.com/
Unofficial Affordable OpenVMS Home Page:
http://www.djesys.com/vms/soho/
Martin Vorlaender
> I believe it also comes with source which would be in one or more of the
> "extraneous" savesets.
It's
LD063.A KITINSTAL, .CLD and .HLP files, examples, release notes
LD063.B source files
LD063.C VMS/Alpha 6.2 files
LD063.D VMS/Alpha 7.1 files
LD063.E VMS/Alpha 7.2 files
LD063.F VMS/Alpha 7.3+ files
LD063.G VMS/VAX 6.2 files
LD063.H VMS/VAX 7.1 files
LD063.I VMS/VAX 7.2 files
LD063.J VMS/VAX 7.3+ files
> I don't yet know if the KITINSTAL.COM for V6.3 still has the "phone
> home" "feature" (bug?).
Not in the KITINSTAL I examined (from the Freeware5 CD).
cu,
Martin
--
Your mouse has moved. | Martin Vorlaender | VMS & WNT programmer
Windows must be restarted | work: m...@pdv-systeme.de
for the change to take | http://www.pdv-systeme.de/users/martinv/
effect. Reboot now? [OK] | home: mar...@radiogaga.harz.de
David J. Dachtera
>
> David J. Dachtera (djesys...@fsi.net) wrote:
> > I believe it also comes with source which would be in one or more of the
> > "extraneous" savesets.
>
> It's
> LD063.A KITINSTAL, .CLD and .HLP files, examples, release notes
> LD063.B source files
> LD063.C VMS/Alpha 6.2 files
> LD063.D VMS/Alpha 7.1 files
> LD063.E VMS/Alpha 7.2 files
> LD063.F VMS/Alpha 7.3+ files
> LD063.G VMS/VAX 6.2 files
> LD063.H VMS/VAX 7.1 files
> LD063.I VMS/VAX 7.2 files
> LD063.J VMS/VAX 7.3+ files
>
> > I don't yet know if the KITINSTAL.COM for V6.3 still has the "phone
> > home" "feature" (bug?).
>
> Not in the KITINSTAL I examined (from the Freeware5 CD).
Thanx! The MicroVAX 3100 and the AlphaStation 200 are both shutdown
right now and I didn't want to take the time to spin one up and unpack
the archive just to look at that.
Wonder if there are any new features in LD V6.3, or is it just a VMS
version support upgrade?
> cu,
> Martin
> --
> Your mouse has moved. | Martin Vorlaender | VMS & WNT programmer
> Windows must be restarted | work: m...@pdv-systeme.de
> for the change to take | http://www.pdv-systeme.de/users/martinv/
> effect. Reboot now? [OK] | home: mar...@radiogaga.harz.de
MAN! *THAT* is a *GREAT* sig! I gotta show that one around...
Martin Vorlaender
> Wonder if there are any new features in LD V6.3, or is it just a VMS
> version support upgrade?
New in V6.3:
$ LD TRACE/FDT (Alpha only)
$ LD TRACE/ACCURATE (Alpha only) - accurate timing of I/O requests
Container files my now reside on NFS volumes.
$ LD CREATE/CONTINUOUS
Restriction on the maximum size of the logical disk without
specifying geometry lifted.
Deleted container files which are still connected can now be
disconnected without /ABORT.
cu,
Martin
P.S.:
> MAN! *THAT* is a *GREAT* sig! I gotta show that one around...
;-)
How 'bout this one:
--
Emacs would be a great | Martin Vorlaender | VMS & WNT programmer
operating system, | work: m...@pdv-systeme.de
if only it came with | http://www.pdv-systeme.de/users/martinv/
a decent editor... | home: mar...@radiogaga.harz.de
Hoff Hoffman
:Just attempted to install LD062 on AXP running 7.3. When the kit is
:unzipped it
:produces LD062.[A-K] but running VMSINSTALL only restores savesets A and E.
:Is this correct?
IIRC, different savesets are used different system configurations -- but
you can pull apart the .A saveset and look in KITINSTAL.COM for details,
or (of course) you can simply try the tool and see if it works.
---------------------------- #include <rtfaq.h> -----------------------------
For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com
--------------------------- pure personal opinion ---------------------------
Hoff (Stephen) Hoffman OpenVMS Engineering hoffman#xdelta.zko.dec.com
Hoff Hoffman
:from David Dachtera's site seems to have some changes made as indicated in
:the Readme, particularly in regards to the creation of the zip file. Has
:this been incorporated in 6.3?
There's a zip file in:
http://www.openvms.compaq.com/freeware/freeware50/ld063/
If you haven't yet had the pleasure of fixing a BACKUP saveset corrupted
by an FTP transfer (trivial, once you know how), please review the pointers
to the tools in the FAQ -- or get a copy of the tool from the Freeware
website or from the Freeware disks (in [000tools...]).
Tom Linden
didn't see that this got answered some days ago. In any event it
appears that this is obsolete anyway and that 063 is the way to go.
> -----Original Message-----
> From: Hoff Hoffman [mailto:hof...@xdelta.zko.dec.nospam]
> Sent: Thursday, March 21, 2002 5:38 PM
> To: Info...@Mvb.Saic.Com
> Subject: Re: LD062 Install Question
>
>
> In article <CIEJLCMNHNNDLLOO...@kednos.com>, "Tom
> Linden" <t...@kednos.com> writes:
> :Just attempted to install LD062 on AXP running 7.3. When the kit is
> :unzipped it
> :produces LD062.[A-K] but running VMSINSTALL only restores
> savesets A and E.
> :Is this correct?
>
> IIRC, different savesets are used different system
> configurations -- but
> you can pull apart the .A saveset and look in KITINSTAL.COM for details,
> or (of course) you can simply try the tool and see if it works.
>
>
Tom Linden
> -----Original Message-----
> From: Hoff Hoffman [mailto:hof...@xdelta.zko.dec.nospam]
> Sent: Thursday, March 21, 2002 5:42 PM
> To: Info...@Mvb.Saic.Com
> Subject: RE: LD062 Install Question
>
>
> In article <CIEJLCMNHNNDLLOO...@kednos.com>, "Tom
> Linden" <t...@kednos.com> writes:
> :Are you recommending to use 6.3 instead of 6.2? The 6.2 kit I downloaded
> :from David Dachtera's site seems to have some changes made as
> indicated in
> :the Readme, particularly in regards to the creation of the zip file. Has
> :this been incorporated in 6.3?
>
> There's a zip file in:
>
> http://www.openvms.compaq.com/freeware/freeware50/ld063/
>
> If you haven't yet had the pleasure of fixing a BACKUP saveset
> corrupted
> by an FTP transfer (trivial, once you know how), please review
> the pointers
> to the tools in the FAQ -- or get a copy of the tool from the Freeware
> website or from the Freeware disks (in [000tools...]).
>
I have had that pleasure, thank you, and in fact on our ftp site
freja.kednos.com
the appropriate script appears multiple times. But it has always struck me
as odd,
that knowing this why not build it directly into backup in the first place?
David J. Dachtera
>
> Thanks, Hoff, but I know you are busy with the Itanium port and
> didn't see that this got answered some days ago. In any event it
> appears that this is obsolete anyway and that 063 is the way to go.
I'll keep the older version available for those who might still need it.
David J. Dachtera
Yes - second the motion, taking a couple of queues from ZIP:
$ BACKUP/FIX_SAVESET[=FULL] saveset_filespec/SAVE_SET
Repair the RMS attributes of a saveset (maybe). ["=FULL" means "try
harder"]
$ BACKUP/TEST_SAVESET saveset_filespec/SAVE_SET
Check the integrity of a saveset.
As usual, back-port the upgrades to V5.5-2 so no one gets left out.
Tom Linden
> -----Original Message-----
> From: David J. Dachtera [mailto:djesys...@fsi.net]
> Sent: Thursday, March 21, 2002 6:42 PM
> To: Info...@Mvb.Saic.Com
> Subject: Re: LD062 Install Question
>
>
> Tom Linden wrote:
> >
> > Thanks, Hoff, but I know you are busy with the Itanium port and
> > didn't see that this got answered some days ago. In any event it
> > appears that this is obsolete anyway and that 063 is the way to go.
>
> I'll keep the older version available for those who might still need it.
Never-the-less since your site is refereenced in the FAQ (and I should add,
is very useful) you may wish to update it.
Bart Zorn
>
> Yes - second the motion, taking a couple of queues from ZIP:
>
> $ BACKUP/FIX_SAVESET[=FULL] saveset_filespec/SAVE_SET
>
> Repair the RMS attributes of a saveset (maybe). ["=FULL" means "try
> harder"]
>
> $ BACKUP/TEST_SAVESET saveset_filespec/SAVE_SET
>
> Check the integrity of a saveset.
>
> As usual, back-port the upgrades to V5.5-2 so no one gets left out.
>
The second function is already present in Save Set Manager with the SAVE
VALIDATE command.
Bart Zorn
Arne Vajhøj
Yes.
I think A = install-script and the rest contains the binaries for each
VMS
version supported - one saveset = one VMS version !
Arne
Alan E. Feldman
[...]
> Yes - second the motion, taking a couple of queues from ZIP:
>
> $ BACKUP/FIX_SAVESET[=FULL] saveset_filespec/SAVE_SET
>
> Repair the RMS attributes of a saveset (maybe). ["=FULL" means "try
> harder"]
>
> $ BACKUP/TEST_SAVESET saveset_filespec/SAVE_SET
>
> Check the integrity of a saveset.
You can use BACKUP/LIST to check the integrity of a save set. Check
out this article:
[begin quote]
Search Result 1
From: Jerry Leichter (leic...@lrw.com)
Subject: RE: How To Verify Integrity of A BACKUP SaveSet
Newsgroups: comp.os.vms
View: Complete Thread (9 articles) | Original Format
Date: 1993-03-26 23:05:35 PST
[original poster's problem:]
One of the groups using the VAXcluster that I manage is creating tape
backups of disks to send out to our new sites. Once the tapes are
created, they want to be able to verify that the tape is: 1) readable
and 2) contains valid data. The best solution I have been able to
come up with is to restore the entire tape to another disk, using the
/Image qualifier (which was used when the tape was created).
[Jerry's response:]
A simple BACKUP/LIST verifies the contents of the save set. Here's
proof:
I created an on-disk saveset named FOO.A, then deliberately damaged
it. Now
watch:
$ back/list foo.a/sav
Listing of save set(s)
Save set: FOO.A
Written by: LEICHTER
UIC: [000110,000051]
Date: 26-MAR-1993 11:36:33.82
Command: BACKUP/NOASSIST *.*; FOO.A/SAVE/LOG
Operating system: VAX/VMS version V5.2
BACKUP version: V5.2
...
[LEICHTER.RUTGERS.CLASSES.315]MID93.DVI;7 23 24-MAR-1993
20:52
[LEICHTER.RUTGERS.CLASSES.315]MID93.LIS;7 3 24-MAR-1993
20:52
[LEICHTER.RUTGERS.CLASSES.315]MID93.LTX;14 24 26-MAR-1993
07:57
>>>> 1 error recovered by redundancy group in
>>>> $DISK1:[LEICHTER.RUTGERS.CLASSES.315]FOO.A;1
Total of 21 files, 103 blocks
End of save set
Before anyone comments that BACKUP only did this because I damaged the
inter-
nal record structure, or something of that sort: No, I was careful.
I
changed one byte in the middle of the data from a file. It was not
even at a
record boundary, not that that would matter. In fact, here's what
DIFFER
reports (after I've used FILE to set the the recordsize to 16 - to
keep the
output to a reasonable length - in both FOO.A and FOO.B, which is a
saved
copy of FOO.A):
File $DISK1:[LEICHTER.RUTGERS.CLASSES.315]FOO.A;1
RECORD NUMBER 71 (00000047) LENGTH 16 (00000010)
72612079 62207564 652E7372 3F677475 utg?rs.edu by ar 000000
RECORD NUMBER 72 (00000048) LENGTH 16 (00000010)
7564652E 73726567 7475722E 73696D61 amis.rutgers.edu 000000
******
File $DISK1:[LEICHTER.RUTGERS.CLASSES.315]FOO.B;1
RECORD NUMBER 71 (00000047) LENGTH 16 (00000010)
72612079 62207564 652E7372 65677475 utgers.edu by ar 000000
RECORD NUMBER 72 (00000048) LENGTH 16 (00000010)
7564652E 73726567 7475722E 73696D61 amis.rutgers.edu 000000
************
Number of difference sections found: 1
Number of difference records found: 1
DIFFERENCES /IGNORE=()/MERGED=1/MODE=(HEXADECIMAL)-
$DISK1:[LEICHTER.RUTGERS.CLASSES.315]FOO.A;1-
$DISK1:[LEICHTER.RUTGERS.CLASSES.315]FOO.B;1
[original poster:]
I'm wondering if anyone has suggestion(s) as to how we can verify the
contents of these tapes without having to allocate another whole disk
to that group? Is there a way to send the info to the NL: device?
[Jerry:]
If you want to be really, really, sure, restore the backup to a disk
with
/VERIFY. That will tell you all you can reasonably hope to learn
about the
integrity of the saveset.
Me, I've found I can trust in BACKUP/LIST.
-- Jerry
[end quote]
--
Dislcaimer: JMHO
Alan E. Feldman
afeldman atski gfigroup dotski com
"Help me help you help me help you" --Bob Patterson