Kbase 10806: How to Check Privileges on VMS that are Installed in Memory
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
GOAL:
How to check privileges set on a VMS installation and correct them if they are wrong.
FACT(s) (Environment):
Open VMS
FIX:
In order to avoid giving users privileges to allow them to run Progress when they might not need them, OpenVMS allows you to install them into memory. This means that the executables have the privileges when they are run, but the user does not.
An indication that the executables are not installed correctly or do not have the correct privileges, are messages such as the following:
insufficient privilege or protection violation.
If you are not sure that the executables have been installed correctly, you can check the installation with the following command:
$ set def sys$system
$ install
INSTALL> list bin:progres.exe /full
DISKNAME:<SYS0.SYSCOMMON.DLC.BIN>.EXE (this is the
physical location on the disk)
PROGRES;1 Open Shar Prv
Entry access count = 0
Current/Maximum shared = 1/0
Global section count = 2
Privileges = SYSPRV SYSLCK GROUP WORLD SYSNAM
SETPRV DETACH SYSGBL
If you are not sure that they have been installed correctly, and you want the customer to check for you, the command you should run is:
INSTALL> list bin:_mprosrv.exe /full
DISKNAME:<SYS0.SYSCOMMON.DLC.BIN>.EXE (this is the
physical location on the disk)
_MPROSRV;1 Open Shar Prv
Entry access count = 0
Current/Maximum shared = 1/0
Global section count = 2
Privileges = SYSPRV SYSLCK GROUP WORLD SYSNAM
SETPRV DETACH SYSGBL
INSTALL> exit
$
The above examples show that commands your executables should be installed with. If they are not correct, you can replace them by issuing the following command:
$
$ install
INSTALL> replace bin:<your executable>
/open/share/priv=(sysprv,
syslck,group,world,sysnam,setprv,detach,sysgbl)
INSTALL> exit
$
If, when you do the list, the following is returned:
INSTALL> list bin:progres.exe
%INSTALL-W-FAIL, failed to LIST entry for <disk>:
<directory.DLC.BIN>PROGRES.EXE
-INSTALL-E-NOKFEFND, Known File Entry not found
INSTALL>
you must install the executable. Use ADD instead of REPLACE in the above command.
Typically you install PROGRES.EXE and _MPROSRV.EXE, although some users also do install _MPRSHUT.EXE.