I'm using freeaxp installed on windows XP virtual machine under virtualbox.
I do have make a backup/image of a physical dec alpha 1000 96MB that run some process using intertask communication and shareable common as detach process.
I do have restored this image on freeaxp and on second disk I have restore the applications backup savet_set.
The system seems to boot up correctly except errors regarding time server and TCP/IP config since I do not have yet modify it to fit new emaulated environnement!
My problem is that when I've try to install shareable common, I got error regarding size mismatched, I got rid of this error by recompiling/relinking all application!
Then when I try to start the application as detached as per on physical alpha I got the following errors:
Message from user AUDIT$SERVER on MACGAL
Security alarm (SECURITY) and security audit (SECURITY) on MACGAL, system id: 10
39
Auditable event: Batch process login failure
Event time: 12-JUN-2012 09:37:45.52
PID: 0000009E
Process name: BATCH_2
Username: USGFIN
Process owner: [USGFIN]
Image name: DSA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE
Status: %RMS-E-PRV, insufficient privilege or file protection
violation
How this append since the crepencies of users are ok on phisical alpha, and I can well login with users login as per on phisical alpha????
Could somebody help me, I've lost most of my skill under openvms since I was not using it since 14 years!!!
In order to build my system I've done the following:
On physical alpha 1000 I've done a backup/image of the system disk.
Then I've create a ISO file containing this image backup
I've mount this iso file under freeaxp, copy the backup/image on empty alpha disk under freeaxp
fix the backup/image file since I transfer it via vaxlink2
then restore the backup/image on my system disk.
Doing this I got a "running" openvms 7.1 under freeaxp, of course since the number os disk are not the same, I do modify in order to point correctly to application disk.
Remain to fix networking
regarding my problem, I do have correctly the system account logging as on physical alpha
I do have also usgfin user logging as on physical alpha.
The boot sequence is as follow:
systartup_vms calling macgal$startup calling lieucom:systart calling $modap:[gfin.com]systartup_gfin
all above go fine until I have the following:
submit $MODAP:[GFIN.COM.TOOL]submit.com/user=USGFIN/param=RUN_PROC_MANAGER/log_file=$MODAP:[GFIN.LOG]run_proc_manager.log/keep
this one generate the error:
%%%%%%%%%%% OPCOM 12-JUN-2012 18:44:01.83 %%%%%%%%%%%
Message from user AUDIT$SERVER on MACGAL
Security alarm (SECURITY) and security audit (SECURITY) on MACGAL, system id: 1039
Auditable event: Batch process login failure
Event time: 12-JUN-2012 18:44:01.82
PID: 00000132
Process name: BATCH_90
Username: USGFIN
Process owner: [USGFIN]
Image name: DSA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE
Status: %RMS-E-PRV, insufficient privilege or file protection violation
Is this a system that is running an industrial automation package?
What it looks like is that something has removed privileges from the SYSTEM account.
One red flag about your configuration is the name $MODAP for a device. That violates VMS naming convention. It is long established that the"$" character in symbols, filenames and logical names is reserved to Digital/Compaq/HP or specific registered third parties. And in the cases of the registered third parties, the "$" character is to be preceded by a prefix registered to that third party.
Since $MODAP is not a known VMS supplied logical name, and does not match the convention for a third party registered name, it means it was set up by someone that violated long standing rules for setting up VMS systems. And if they got something as simple as that wrong, what did they do with the more complicated issues?
This means that there could be many unknown issues in your original system setup.
My recommendation is that you hire an experienced VMS professional that can visit your site.
If you subscribe to http://listserv.encompassus.org/scripts/wa-ENCOMPASS.exe?A0=VMS-SIG , you may be able to get more help than in this forum, as that mailing list is where the professionals give advice.
That is also the place to get a reliable recommendation for a consultant to do a site visit.
This forum is mainly for non-professional hobbyists that run VMS on their personal machines.
I have over 25 years in doing industrial automation on VMS, and every time I have found a system with illegal logical names on it, I have found many major problems with the installation, and it has taken quite a bit of planning and time to do a repair of the system. In many cases I was very surprised at how much a VMS system disk could be corrupted, yet the system was still able to do production work.
I even do not know that $modap do not follow rules. Apparently none of vax or alpha system I've been in the past follows this rules.
I do finaly fix the problem, since I do not create application disk backup as backup/image, when I restore it even with /by_owner=original, all the file where owned by system with no write to the user that should used them.
Temporaly I set protection of file that everybody can do anything (who care, I'm the only one using this emulated alpha) and it's work (at least for batch submit).
The fact is then that freeaxp 32 bits under virtualbox (emulating 3 CPU) on a physical laptop 4MB with core I5 face a problem of CPU, I got 99% CPU when all process loaded!!!!!
The same system, with freeaxp 64bits directly install on Windows7 64bits is OK regarding the CPU loaded.
So now I do have to focus myself on the network configuration on emulated alpha, so that alpha may communicate with host windows.
malmberg August 04 2022 No more VAX hobbyist licenses. Community licenses for Alpha/IA64/X86_64 VMS Software Inc. Commercial VMS software licenses for VAX available from HPE.
ozboomer July 20 2022 Just re-visiting.. No more hobbyist licenses? Is that from vmssoftware.com, no 'community' licenses?
valdirfranco July 01 2022 No more hobbyist license...sad
mister_wavey February 12 2022 I recall that the disks failed on the public access VMS systems that included Fafner
parwezw January 03 2022 Anyone know what happened to FAFNER.DYNDS.ORG? I had a hobbyist account here but can longer access the site.
gtackett October 27 2021 Make that DECdfs _2.1A_ for Vax
gtackett October 27 2021 I'm looking for DECdfs V2.4A kit for VAX. Asking here just in case anyone is still listening.
MarkRLV September 17 2021 At one time, didn't this web site have a job board? I would love to use my legacy skills one last time in my career.
malmberg January 18 2021 New Hobbyist PAKs for VAX/VMS are no longer available according to reports. Only commercial licenses are reported to be for sale from HPE
dfilip January 16 2021 Can someone please point me to hobbyist license pak? I'm looking for VAX/VMS 7.1, DECnet Phase IV, and UCX/TCPIP ... have the 7.1 media, need the license paks ... thanks!
