Posts: 8 Location: Vienna, Austria Joined: 03.02.09
Posted on November 04 2010 11:26
Hi all,
I'm having issues with adding/creating a new user on my hobbyist system running OpenVMS VAX 7.1
I've tried adding a new user using the UAF utility (mc authorize) as well as with the ADDUSER.COM DCL procedure.
The new user can be found in the UAF:
...but when I try to login with this new user, I keep getting an OPCOM message like following:
%%%%%%%%%%% OPCOM 4-NOV-2010 22:08:33.79 %%%%%%%%%%%
Message from user AUDIT$SERVER on DECVAX
Security alarm (SECURITY) and security audit (SECURITY) on DECVAX, system id: 30
300
Auditable event: Remote interactive login failure
Event time: 4-NOV-2010 22:08:33.78
PID: 00000215
Process name: _TNA5:
Username: <login>
Terminal name: TNA5:, _TNA5:, -deleted my ip-
Status: %LOGIN-F-NOSUCHUSER, no such user
Am I missing something important? Hope you can help me to solve this issue.
Posts: 134 Location: Hopedale, MA USA Joined: 15.12.05
Posted on November 04 2010 14:32
Could you provide a screen shot of the actual login session?
$help/message nosuchuser reveals:
NOSUCHUSER, no such user
Facility: LOGIN, Login Procedure
Explanation: The specified user name does not exist. This message is
written to the system accounting and security audit records;
the NOTVALID message displays to the user.
A possible cause: Your UAF and the one that LOGIN uses are not the same. LOGIN by default uses the file SYS$SYSTEM:SYSUAF.DAT (if the logical SYSUAF isn't defined), while AUTHORIZE works on the file SYS$DISK:[]SYSUAF.DAT. So one must always remember to SET DEFAULT SYS$SYSTEM: before running AUTHORIZE.
Now, if the logical SYSUAF is defined, it has to be defined /SYSTEM/EXEC for LOGIN and AUTHORIZE to use the same file.
Posts: 8 Location: Vienna, Austria Joined: 03.02.09
Posted on November 05 2010 23:29
brad wrote:
Could you provide a screen shot of the actual login session?
Hi brad,
it's not 100% clear for me, what you do mean.
The actual login session was the one where I was logged on as SYSTEM, but which screen exactly?
martinv2 wrote:
A possible cause: Your UAF and the one that LOGIN uses are not the same. LOGIN by default uses the file SYS$SYSTEM:SYSUAF.DAT (if the logical SYSUAF isn't defined), while AUTHORIZE works on the file SYS$DISK:[]SYSUAF.DAT. So one must always remember to SET DEFAULT SYS$SYSTEM: before running AUTHORIZE.
Now, if the logical SYSUAF is defined, it has to be defined /SYSTEM/EXEC for LOGIN and AUTHORIZE to use the same file.
HTH
Martin
Hi Martin,
excellent! Very good explanation/instruction. Following it I could add a new user immediately. Worked like a charm. Thanks a lot!
Kind regards,
dec_at
Edited by dec_at on November 05 2010 23:32
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!
