VAX VMS 6.2 - recreate UAF and Rightslist

[Dave_56]

Hi all,
I have an old Vax I have fired up & want to provide for students to muck around with.
I have a feeling either the UAF or rightslist is corrupt, because if I change protection on a directory - all looks good, but when I log in as the user that should have permissions to the directory and try to set def to that dir, access is denied.

Is there a quick way to blow away the UAF and Rightslist and recreate? There is no users/rights I'm interested in keeping.

Or can anyone offer any other suggestion.

Thanks!
Dave

[Mobeen_1]

Dave,
Here are the answers to your questions

Recreating SYSUAF
-----------------
1. Make a backup copy of your SYSUAF file
2. Create an FDL of SYSUAF using
the command
anal/rms/fdl
3. Make sure nobody is accessing SYSUAF.
4. convert/fdl of the new sysuaf file


Recreating RIGHTSLIST
----------------------
UAF> CREATE/RIGHTS
{message}
UAF> ADD/IDENTIFIER/USER=* or ADD/IDENTIFIER/USER=[*,*]
{messages}

rgds
Mobeen

[Dave_56]

Thanks Mobeen, I will give these a try .


Appreciate your response.

[Jan van den Ende]

Well,

since you want to get rid of ALL your old info, you really want a new INITIAL file.

If you use a CONVERT/FDL, all old info is in your new file.
If you do a CREATE/FDL, then NO info is in the new file.
You need, however, a file with initial records.

From a suitably priv'd account, you can rename your SYSUAF file away. First: is the logical name SYSUAF defined? If not, then you will want a SET DEFAULT SYS$COMMON:[SYSEXE], because that is where the file is looked for if not defined.
Rename SYSUAF.DAT to (eg.) SYSUAF.OLD
If you now run AUTHORIZE, you will get a message/question "SYSUAF NOT FOUND. CREATE IT?"
Answer YES, and you will have a clean authorisation file, containing the required records.
Most important: an account named DEFAULT.
Why is that important? You want to be able to ADD new accounts, but actually, that is implemented as: COPY DEFAULT => new_name.
That is also how you get all your default settings for new accounts.

For RIGHTSLIST you follow Mobeen's instructions.

Depending on previous usage of your system, you might also wish to delete NETPROXY.DAT (if DECnet phase IV) or NET$PROXY.DAT (phase V).
Those are also created if needed & missing.

Success!


Jan

[Ian Miller.]

you may find a SYSUAF.TEMPLATE which can be copied to SYSUAF.DAT
CRE/RIGHTS and CRE/PROXY in AUTHORIZE will get you a new RIGHTSLIST.DAT and NETPROXY.DAT

[Dale A. Marcy]

Dave,

Do you have a process logical defined for SYSUAF? If so, then what could be happenning is that you make the changes based on the file pointed to by that logical, but when you log in under the other user, you get the copy of the SYSUAF.DAT that is in Sys$System:.

[Dave_56]

Thanks all. I'll post back when I've had a play.