<div dir="auto">SLAVE is a free axp instance running on a Windows virtual machine. <div dir="auto"><br></div><div dir="auto">Unfortunately I have intermittent networking issues with this setup which I have yet to get to the bottom of. The archive you've retrieved is from a SIMH Vax VMS instance running on a HP microserver running Debian. <div dir="auto"><br></div><div dir="auto">Glad you got what you needed. I'll take another look at the networking for SLAVE</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 20 Oct 2020, 02:35 Supratim Sanyal, <<a href="mailto:supratim@riseup.net">supratim@riseup.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10/19/20 8:54 PM, David Moylan wrote:<br>
<br>
> I think I've managed to hunt this down.<br>
><br>
> I'll show you how I got there, because it's a useful path.<br>
><br>
> I first went to Martin's ConDist CD list:<br>
> <a href="http://de.openvms.org/martinv/VMS_CD_KITS.html" rel="noreferrer noreferrer" target="_blank">http://de.openvms.org/martinv/VMS_CD_KITS.html</a><br>
><br>
> and looked for "PCSA" and found two 041 releases. These are on the CDBIN04SEP2 and CDBIN10NOV2 distributions respectively.<br>
><br>
> I then went searching for these two distributions and got a hit on an archived HECnet post on <a href="http://hecnet.eu" rel="noreferrer noreferrer" target="_blank">hecnet.eu</a> from 2013 by Mark Wickens.<br>
> It says the CDBIN10NOV2 is available on SLAVE:: (which appears not to be online), but also gives an http link to the associated archive.<br>
><br>
> <a href="http://hecnet.eu/archive/VAX_MEDIA/1992_nov_cdbin10nov2/" rel="noreferrer noreferrer" target="_blank">http://hecnet.eu/archive/VAX_MEDIA/1992_nov_cdbin10nov2/</a><br>
><br>
> and so I searched through the directories and found:<br>
><br>
> <a href="http://hecnet.eu/archive/VAX_MEDIA/1992_nov_cdbin10nov2/cdbin10nov27/pcsa041/kit/" rel="noreferrer noreferrer" target="_blank">http://hecnet.eu/archive/VAX_MEDIA/1992_nov_cdbin10nov2/cdbin10nov27/pcsa041/kit/</a><br>
> <a href="http://hecnet.eu/archive/VAX_MEDIA/1992_nov_cdbin10nov2/cdbin10nov27/pcsau1041/kit/" rel="noreferrer noreferrer" target="_blank">http://hecnet.eu/archive/VAX_MEDIA/1992_nov_cdbin10nov2/cdbin10nov27/pcsau1041/kit/</a><br>
><br>
> I hope that's what you were looking for :-)<br>
><br>
> Cheers, Wiz!!<br>
<br>
Awesome, Wiz! Thank you.<br>
<br>
$ @DUA0:[TOOLS]<a href="http://RESET_BACKUP_SAVESET_ATTRIBUTES.COM" rel="noreferrer noreferrer" target="_blank">RESET_BACKUP_SAVESET_ATTRIBUTES.COM</a> PCSA041.A<br>
$ @DUA0:[TOOLS]<a href="http://RESET_BACKUP_SAVESET_ATTRIBUTES.COM" rel="noreferrer noreferrer" target="_blank">RESET_BACKUP_SAVESET_ATTRIBUTES.COM</a> PCSA041.B<br>
$ SET PROC/PRIV=ALL<br>
$ @SYS$UPDATE:VMSINSTAL<br>
<br>
<br>
OpenVMS VAX Software Product Installation Procedure V7.3<br>
<br>
<br>
It is 19-OCT-2020 at 21:13.<br>
<br>
Enter a question mark (?) at any time for help.<br>
<br>
%VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.<br>
%VMSINSTAL-W-ACTIVE, The following processes are still active:<br>
WWW server 80<br>
OSUHTTPD_1<br>
SERVER_000B<br>
SERVER_000A<br>
* Do you want to continue anyway [NO]? YES<br>
* Are you satisfied with the backup of your system disk [YES]?<br>
* Where will the distribution volumes be mounted: DUB0:[STORAGE]<br>
<br>
Enter the products to be processed from the first distribution volume set.<br>
* Products: *<br>
* Enter installation options you wish to use (none):<br>
<br>
The following products will be processed:<br>
<br>
PCSA V4.1<br>
<br>
<br>
Beginning installation of PCSA V4.1 at 21:14<br>
<br>
%VMSINSTAL-I-RESTORE, Restoring product save set A ...<br>
%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.<br>
%PCSA-I-VERSION, Checking for VMS version 5.3 or greater...<br>
* Do you want to run the IVP after the installation [YES]?<br>
* Do you want to purge files replaced by this installation [YES]?<br>
%PCSA-I-FREEBLKS, Checking for 7000 free blocks<br>
%PCSA-I-CHK_NET, Checking if DECnet is running<br>
* Disk Name for PCSA system/application software [SYS$SYSDEVICE]:<br>
* Disk Name for User accounts, COMMON services [SYS$SYSDEVICE]:<br>
* Group number for PCFS software directories [360]:<br>
* Disk Name for LAD BOOT disks [SYS$SYSDEVICE]:<br>
<br>
All questions have been answered.<br>
The installation of PATHWORKS for VMS S4.1C<br>
will continue.<br>
<br>
<br>
%VMSINSTAL-I-RESTORE, Restoring product save set B ...<br>
<br>
%PCSA-I-DIRECTORY, Checking for [PCSA] on the system disk<br>
%VMSINSTAL-I-SYSDIR, This product creates system directory [PCSA].<br>
<br>
If you intend to execute this layered product on other nodes in your<br>
OpenVMS Cluster, and you have the appropriate software license, you <br>
must<br>
prepare the system-specific roots on the other nodes by issuing the<br>
following command on each node (using a suitably privileged account):<br>
<br>
$ CREATE /DIRECTORY SYS$SPECIFIC:[PCSA]<br>
%PCSA-I-CRE_RBDB, Creating the Remote Boot Service Database<br>
%PCSA-I-CRE_ACF, Creating the File Service Database<br>
%PCSA-I-CRE_LAD_ACF, Creating the Local Area Disk Service Database<br>
%PCSA-I-INITIAL, Creating the initial Server directory structure<br>
%VMSINSTAL-I-SYSDIR, This product creates system disk directory <br>
SYS$SYSDEVICE:[PCFS_SPOOL].<br>
%VMSINSTAL-I-SYSDIR, This product creates system disk directory <br>
SYS$SYSDEVICE:[PCFS_SPOOL.DEFAULT].<br>
%VMSINSTAL-I-SYSDIR, This product creates system disk directory <br>
SYS$SYSDEVICE:[PCSA].<br>
%VMSINSTAL-I-SYSDIR, This product creates system disk directory <br>
SYS$SYSDEVICE:[PCSA.LAD].<br>
%VMSINSTAL-I-SYSDIR, This product creates system disk directory <br>
SYS$SYSDEVICE:[LADBOOT].<br>
%VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named <br>
PCFS$ACCOUNT.<br>
%UAF-I-ADDMSG, user record successfully added<br>
%UAF-I-RDBADDMSGU, identifier PCFS$ACCOUNT value [000360,000001] added <br>
to rights database<br>
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named <br>
PCFS$ACCOUNT.<br>
%UAF-I-MDFYMSG, user record(s) updated<br>
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named <br>
PCFS$ACCOUNT.<br>
%UAF-I-MDFYMSG, user record(s) updated<br>
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named <br>
PCFS$ACCOUNT.<br>
%UAF-I-MDFYMSG, user record(s) updated<br>
%VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named PCSA$RMI.<br>
%UAF-I-ADDMSG, user record successfully added<br>
%UAF-I-RDBADDMSGU, identifier PCSA$RMI value [000360,000002] added to <br>
rights database<br>
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCSA$RMI.<br>
%UAF-I-MDFYMSG, user record(s) updated<br>
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCSA$RMI.<br>
%UAF-I-MDFYMSG, user record(s) updated<br>
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCSA$RMI.<br>
%UAF-I-MDFYMSG, user record(s) updated<br>
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named PCSA$RMI.<br>
%UAF-I-MDFYMSG, user record(s) updated<br>
%VMSINSTAL-I-ACCOUNT, This installation adds an identifier named PCFS$READ.<br>
%UAF-I-RDBADDMSG, identifier PCFS$READ value %X80010005 added to rights <br>
database<br>
%VMSINSTAL-I-ACCOUNT, This installation adds an identifier named <br>
PCFS$UPDATE.<br>
%UAF-I-RDBADDMSG, identifier PCFS$UPDATE value %X80010006 added to <br>
rights database<br>
%VMSINSTAL-I-ACCOUNT, This installation adds an identifier named <br>
NETBIOS$ACCESS.<br>
%UAF-I-RDBADDMSG, identifier NETBIOS$ACCESS value %X80010007 added to <br>
rights database<br>
%VMSINSTAL-I-ACCOUNT, This installation adds an identifier named PCFS$USER.<br>
%UAF-I-RDBADDMSG, identifier PCFS$USER value %X80010008 added to rights <br>
database<br>
%PCSA-I-CRE_PARAMS, Creating Service Parameter Database<br>
%PCSA-I-CRE_PCFS_LOG, Creating <a href="http://PCFS_LOGICALS.COM" rel="noreferrer noreferrer" target="_blank">PCFS_LOGICALS.COM</a><br>
%PCSA-I-CRE_LAD_LOG, Creating <a href="http://LAD_LOGICALS.COM" rel="noreferrer noreferrer" target="_blank">LAD_LOGICALS.COM</a><br>
%PCSA-I-DEF_OBJS, Defining DECnet objects PCFS,PCSA$RMI,PCX$SERVER,and <br>
PCSA$MAIL<br>
%PCSA-I-SPECIFY, Specifying target directories for the appropriate files<br>
%PCSA-I-REPLACE, PCFS$STARTUP_PARAMS.DAT has been replaced<br>
<br>
POST INSTALLATION INSTRUCTIONS<br>
<br>
In order to complete the installation of PATHWORKS for VMS<br>
you must invoke the PCSA$CONFIG utility as documented in<br>
the installation guide.<br>
<br>
$ @SYS$STARTUP:PCSA$CONFIG<br>
<br>
After running PCSA$CONFIG you may start the file server using<br>
the specified transport(s):<br>
<br>
For DECnet, @SYS$STARTUP:PCFS_STARTUP<br>
For TCP, @SYS$STARTUP:PCFS_STARTUP TCP<br>
For DECnet and TCP, @SYS$STARTUP:PCFS_STARTUP DECNET/TCP<br>
<br>
To start the disk server: @SYS$STARTUP:LAD_STARTUP<br>
* Press RETURN to complete the installation:<br>
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target <br>
directories...<br>
<br>
Starting Installation Verification Procedure<br>
for PATHWORKS for VMS V4.1 at 19-OCT-2020 21:25<br>
<br>
IVP Completed Successfully at 19-OCT-2020 21:25<br>
<br>
Installation of PCSA V4.1 completed at 21:25<br>
<br>
Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY<br>
<br>
Enter the products to be processed from the next distribution volume set.<br>
* Products:<br>
<br>
<br>
<br>
<br>
<br>
<br>
><br>
>> -----Original Message-----<br>
>> From: <a href="mailto:owner-hecnet@Update.UU.SE" target="_blank" rel="noreferrer">owner-hecnet@Update.UU.SE</a> [mailto:<a href="mailto:owner-" target="_blank" rel="noreferrer">owner-</a><br>
>> <a href="mailto:hecnet@Update.UU.SE" target="_blank" rel="noreferrer">hecnet@Update.UU.SE</a>] On Behalf Of Wilm Boerhout<br>
>> Sent: Tuesday, 20 October 2020 1:56 AM<br>
>> To: HECnet List<br>
>> Subject: [HECnet] Pathworks for VMS V4.1 kit anywhere ?<br>
>><br>
>> Hi folks,<br>
>><br>
>> I have become the proud owner of a VAXmate workstation, with a disk<br>
>> enclosure pizzabox attached.<br>
>><br>
>> It is working in that it attempts to boot from disk (which fails), and<br>
>> then boots from the network, and I see a load request coming in on my VAX.<br>
>><br>
>> Now I am looking for the supporting software.<br>
>><br>
>> It looks like Pathworks V4.1 could be of use. I have tracked a kit<br>
>> PCSACLIENT041 (.A and .B), but it requires the PCSA041 server kit, of<br>
>> which, oddly enough, I do have .B but not .A<br>
>><br>
>> Is the PCSA041 kit available on HECnet somewhere ?<br>
>><br>
>><br>
>> *Wilm*<br>
>><br>
-- <br>
Supratim Sanyal, W1XMT<br>
39.19151 N, 77.23432 W<br>
QCOCAL::SANYAL via HECnet<br>
<br>
</blockquote></div>