[an error occurred while processing this directive]

HP OpenVMS Systems

ask the wizard
Content starts here

INSTALL, SYSNAM, lib$set_logical, V7.2?

» close window

The Question is:

 
VMS 7.2 Actually, but no choice on the menu...
Time to update!!!
 
TITLE:  VMS 7.2 Installed Image Privilege recognition (SYSNAM)--NOT!! NEW
FEATURE
 
Dear Mr. Wizard...
 
Since no one from DEC seems to want to take this on comp.os.vms...I thought
I would try here...
 
I think there is a problem in VMS 7.2 Image privilege recognition.
Basically, I want to install a program with SYSNAM privilege to
create a logical name in the LNM$SYSTEM table.
 
If I run this program with SYSNAM privilege, it works as expected;
HOWEVER, if I install the program with SYSNAM privilege, and run from a
non-privileged account, I get
a return of SS$_NOPRIV.  The installed program WORKS under VMS 6.1,
for example.
 
If I modify this program to explictly call $setprv_s for SYSNAM before the
lib$set_logical call, then this program works if installed with SYSNAM for a
non-privileged user.  This is at a minimum an 'undocumented feature' of 7.2,
but I think it is a BUG. T
his is going to cause me untold grief for my customers who will need modify
user accounts or have some other work-around.
 
I have not tried this on VMS 7.2 /VAX yet, only on ALPHA.
 
Below is my test program (not pretty, but illustrative).
 
 
	.title	test
	.psect	data,noexe,rd,wrt
 
name:	.ascid	&TESTLOG&
eqv:	.ascid	&TESTEQV&
table:	.ascid	&LNM$SYSTEM&
 
	.psect	code,exe,rd,nowrt
 
	.entry	test,0
 
	pushl	#0
	pushl	#0
	pushaq	table
	pushaq	eqv
	pushaq	name
 
	calls #5,g^lib$set_logical
 
	$exit_s	r0
 
	.end	test
 
Could someone please tell me if I am missing something here??
 
TIA.
 
Ken Randell
 


The Answer is :

 
  Neither Ask The Wizard nor Comp.os.vms are entirely reliable problem
  reporting mechanisms.  Though the Wizard as well as certain of the Compaq
  folks that frequent comp.os.vms might wish otherwise, postings and
  discussions are sometimes missed.  If you wish to make a formal problem
  report, please contact the Compaq customer support center directly.
 
  This problem is resolved in an available update kit for OpenVMS V7.2.
 

answer written or last revised on ( 12-JUL-1999 )

» close window