More info for RMS-E-PRV

[Stephen Daddona]

One of our programmers is getting a "-RMS-E-PRV, insufficient privilege or file protection violation" message on a compile. I vaguely remember from a few years ago someone from then-Compaq VMS help telling how to get more info on what exactly is generating the error. Can anyone help me on this, or is my memory wrong on this?

Thanks!

[Hein van den Heuvel]

Well, a well behaved VMS application woudl have reported details. For example:

$ set prot=(w,o,g,s) tmp.tmp
$ dir/prot/nohead/notrai/wid=fil=25 tmp.tmp.
U$1:[HEIN]TMP.TMP;12 (,,,)
$ type tmp.tmp
%TYPE-W-OPENIN, error opening U$1:[HEIN]TMP.TMP;12 as input
-RMS-E-PRV, insufficient privilege or file protection violation

If that information is not there, you may want to use the AUDIT subsystem for detailed object access failure reporting.
Something like: $SET AUDIT /ENABLE=ACCESS=FAIL

If to he user with the problem can temporarely be given CMKRNL, then I would use SET WATCH FILE/CLA=MAJOR to see which file cause the problem.

hth,
Hein.

[Verne Britton]

Some languages (C comes to mind) make use of libraries and Include statements that refer to other files on the system (and those items may refer to yet additional files) ...

No offense intended but the message means what it means ... one of the files that is attempted to be accessed is not able to be accessed ...

Can you give us more details ... VMS version, language and version, simple or complicated program, did it ever work before?

How about trying the compile from another user's account ?

[Garry Fruth]

To extend on the response from Hein:

$ SHOW AUDIT/ALARM !Note current config
$ REPLY/ENABLE=SECURITY
$ SET AUDIT/ALARM/ENABLE=ACCESS=FAIL
$ SET AUDIT/ALARM/ENABLE=PRIV:FAIL
$ do your compile - you should see messages regarding file access failures or privilege failures.
$ SET AUDIT/ALARM ... !back to original config

You will need at least OPER & SECURITY privs.

You may want to refer to the "OpenVMS Guide to System Security".

[Stephen Daddona]

The replies helped me find the offending file, which I was able to fix the protections on. I'll make sure that I save the solution this time!


Thanks to all!