[Info-vax] VMSKITBLD.COM fails with CREATE_SYSDIRS cannot locate product description file.

[Dave Froble]

On 1/13/2019 10:47 AM, Andrew Back wrote:
> On Sunday, 13 January 2019 15:41:15 UTC, Dave Froble  wrote:
>> On 1/13/2019 9:58 AM, Andrew Back wrote:
>>> Hello,
>>>
>>> Attempting to get OpenVMS 7.3 installed on a VS2000 via a SimH VAX running on a Linux host. I've created a cluster and added the VS as a satellite node, with page and swap on the SimH node. OpenVMS 7.3 was installed via the Hobbyist kit ISO and opted to install everything in full.
>>>
>>> Everything seems fine up until trying to use VMSKITBLD.COM to build a system disk on the RD53 installed in the VS (KEN). Tried running this from both the simulated VAX and the VS2000, with the same result. Details below and any suggestions much appreciated.
>>>
>>> Cheers,
>>>
>>> Andrew
>>>
>>> //
>>>
>>> $ show dev d
>>>
>>> Device                  Device           Error    Volume         Free  Trans Mnt
>>>    Name                   Status           Count     Label        Blocks Count Cnt
>>> BOB$DUA0:               Mounted              0  OVMSVAXSYS     1714527   159   2
>>> BOB$DUA1:               Online               0
>>> BOB$DUA2:               Online               0
>>> BOB$DUA3:               Online               0
>>> BOB$DYA0:               Online               0
>>> BOB$DYA1:               Online               0
>>> KEN$DUA0:               Online               0
>>> $
>>> $ @sys$update:vmskitbld
>>> * Operation [BUILD,ADD,COPY]? ADD
>>> * Enter mounted SOURCE disk name (ddcu:): sys$sysdevice:
>>> * Enter SOURCE top level system directory [default = SYS0]:
>>> * Enter TARGET disk name (ddcu:): ken$dua0:
>>> * Enter TARGET disk top level system directory [default = SYS0]:
>>> %DCL-I-ALLOC, _KEN$DUA0: allocated
>>> %MOUNT-I-MOUNTED, OVMSVAXSYS mounted on _KEN$DUA0:
>>>       Creating system directories ...
>>> CREATE_SYSDIRS cannot locate product description file
>>>
>>>           ERROR or Control-Y signaled.
>>>
>>>           All files were not copied to the target disk.
>>>
>>> %SYSTEM-F-ABORT, abort
>>> $
>>>
>>
>> It's been a real long time, but, I'm confused.  You wrote that you're
>> trying to install VMS on the local disk.  Why are you using kit build?
>> And if you're trying to build a kit, why are you choosing ADD?
>
> Apologies, the cut and paste shows ADD, but I also tried with BUILD and got the same result.
>
>> If you've already got VMS installed on the SimH system, you could just
>> do an image copy to the local disk.
>
> I have also attempted backup/image/ignore=int bob$dua0: ken$dua0. This fails with an error about cluster size, when both source and target disks indicate this to be 9 from a show dev/full.

For an RD53, I'd initialize it with a clustersize of 1.  The default 
back in the day was 3.  For such a small (tiny) disk, a clustersize of 9 
just might not work.

You can do the image restore without it re-initializing the disk.

check the help, HELP BACKUP /IMAGE

there is the /noinit and noalias stuff to consider

I'm not sure a full install will fit on the RD53

>> I seem to recall that VMSINSTAL would be used to install VMS on a
>> system, from a kit.
>
> I thought this was just for layered products. Do you have details of how to use this to install VMS to a new system disk?

Steve wrote about this.


-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486