Cannot install basic

[Sergio E. Pereda Saviñó]

Hi,

I have a partition rx7640 with openVMS 8.3, and i'm trying to install basic016 with the command @vmsinstall, but im getting the next error:

I copied via ftp the installation files to a directory sys$sysdevice:[000000.temporal]
Im trying to install with this command

$ @VMSINSTAL BASIC016 DKD500:[000000.TEMPORAL] OPTIONS N

... and i'm getting the next error:

Beginning installation of BASIC V1.6 at 20:47

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%BACKUP-E-POSERROR, error positioning DKD500:[000000.TEMPORAL]basic016.a;1
-RMS-F-IOP, operation invalid for file organization or device
%BACKUP-E-READERR, error reading DKD500:[000000.TEMPORAL]basic016.a;1
-BACKUP-E-BLOCKCRC, software block CRC error
%BACKUP-E-INVBLKSIZE, invalid block size in save set
%BACKUP-E-INVRECSIZ, invalid record size in save set
%BACKUP-E-INVRECSIZ, invalid record size in save set
%BACKUP-E-POSERROR, error positioning DKD500:[000000.TEMPORAL]basic016.a;1
-RMS-F-IOP, operation invalid for file organization or device
%BACKUP-E-POSERROR, error positioning DKD500:[000000.TEMPORAL]basic016.a;1
-RMS-F-IOP, operation invalid for file organization or device
%BACKUP-E-READERR, error reading DKD500:[000000.TEMPORAL]basic016.a;1
-BACKUP-E-HDRCRC, software header CRC error
%BACKUP-E-INVBLKSIZE, invalid block size in save set
%BACKUP-E-INVRECSIZ, invalid record size in save set
%BACKUP-E-READERRS, excessive error rate reading DKD500:[000000.TEMPORAL]basic01
6.a;1
-BACKUP-E-HDRCRC, software header CRC error
%BACKUP-I-SPECIFY, specify option (QUIT or CONTINUE)
BACKUP>

can someone help me, im stuck on this =(

Thank you very much,

also im trying to install with a cd-rom but i'm not seeing my cdrom, i think openvms isn't refreshing my disk, i rebooted the system but im still not seeing my cdrom =(

[John Gillings · Accepted solution]

Sergio,

If you copied the VMSINSTAL savesets via FTP, then you've most likely broken the RMS file attributes, so BACKUP isn't recognising it as a valid saveset. More than likely BACKUP/LIST will give you a similar error.

Since you're running V8.3, you can use BACKUP to repair the savesets:

$ BACKUP/LIST/REPAIR DKD500:[TEMPORAL]BASIC016.A/SAVE

(repeat for .B, .C, etc...)

As long as you get reasonable looking listings your VMSINSTAL should work.

Not seeing the CD drive sounds like a hardware issue.

[Willem Grooters]

Using FTP, you MUST use binary mode to copy files (unless you are absolutely sure it is a text file that requires some conversion).

If you receive a VMS ZIP file, it's better to copy that file to VMS and unzip it there than unzipping it on any other platform and copy the files. If properly done, all file attributes are restored with the files.
If yourkit comes from a CD, use that CD (unles you have no CD drive in your box - than above applies).

Savesets for vmsinstal are basically BACKUP savesets and you must have attributes set in place. John gave the righ commadn for that (Even running 8.3 I still use
$ SET FILE/ATTRIB=(LRL:32256) .*, but the built-in is more appropiate).

On your CD: Does the SRM console recognize the drive? If it is a SCSI one, checking your SCSI controllers should mention your attached drives as well. If the drive isn't mentioned, check whether it is actually connected: When you boot, the front access LED should light up some time - no matter whether it's IDE or SCSI.
If you have an IDE CD-rom in an older system, it may be that your firmware does not access IDE drives.

Don't forget that you will need to MOUNT the CD drive to access the CD - there is (AFAIK) no auto-mount facility for removable media.

[Robert Gezelter]

Sergio,

As has been said, most likely the file attributes got damaged during the file transfer. Reset the file attributes using either SET FILE or the BACKUP feature, as has been previously noted.

When I need to do this, I generally do a BACKUP/LIST of each saveset. If there are any residual problems, they show up as errors. Then retry the install.

- Bob Gezelter, http://www.rlgsc.com

[labadie_1]

Before doing a vmsinstal, I usually do
$ backup/lis saveset.a/sav
and the same for all the savesets, to be sure I can read them.

Only the paranoid survive, as said Andy Groove :-)

[John Reagan]

Backup in V8.3 has a /REPAIR qualifier that will attempt to fix savesets that were FTP'd, etc.

Prior to using VMSINSTAL, try a

$ backup/repair/list

on each of the BASIC savesets. See if that helps.

[Sergio E. Pereda Saviñó]

It was the problem of passing the files via FTP, with the backup /repair i could install basic without problem, and the CD-ROM (SCSI) I'd a tape connected also and was making noise to my cd-rom. =)

Thank You very much to all!,

[John Gillings]

Willem,

>Even running 8.3 I still use
>$ SET FILE/ATTRIB=(LRL:32256) .*

I would strongly recommend you cure yourself of this bad habit.

Blindly blasting in the value you assume to be the block size is going to bite you some day.

Yes, MOST savesets use LRL=32256, but not necessarily all. BACKUP/REPAIR, or, on older versions, Hein's FIXSAVESET.COM extract the correct block size from the saveset header.

"It's worked for years" is not an excuse for doing something a in a potentially incorrect and error prone way, when doing it correctly is so simple.