[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ozrock::x25_avms

Title:	DEC X.25 for OpenVMS AXP

Moderator:	OZROCK::MUGGERIDGE

Created:	Mon Jan 18 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	524
Total number of notes:	2218

501.0. "qio with io$_access fails with nopriv" by CSC32::KLIMAS () Wed Mar 05 1997 13:39

    V1.0g, customer claims that he has the psi$x25_user and psi$declname
    identifiers granted his process but a qio with a io$_access modifier
    fails with a nopriv status.  If he has bypass privilege it all works.
    Any reports of this happening that anyone knows of?  
    
    Any help appreciated.
    
    Douglas Klimas
    MCI Mission Critical support

T.R Title User Personal
Name Date Lines

501.1 OZROCK::HARTWIG Arthur Hartwig, TaN Engineering-Australia Wed Mar 05 1997 18:36 17

T.R	Title	User	Personal Name	Date	Lines
501.1		OZROCK::HARTWIG	Arthur Hartwig, TaN Engineering-Australia	`Wed Mar 05 1997 18:36`	17
	Last report I had of this sort of problem was on a clustered system on which someone played around with logicals so that the numeric value of PSI$X25_USER was different at system startup when NWDRIVER was loaded from what it was when the process was created. Of course, this possibility was strongly denied (for a time). But the bottom line is that immediately after X25$NWDRIVER is loaded an application tells X25$NWDRIVER the numeric value of the rights identifiers PSI$X25_USER and PSI$DECLNAME. Thereafter processes wanting to use X.25 should have the appropriate numeric rights identifier. The other possibility is that the X.25 security may be configured such that PSI$X25_USER is insufficient to allow X.25 calls to the selected DTE and DTE address.

Last report I had of this sort of problem was on a 
clustered system on which someone played around with 
logicals so that the numeric value of PSI$X25_USER 
was different at system startup when NWDRIVER was 
loaded from what it was when the process was created.

Of course, this possibility was strongly denied (for a time).

But the bottom line is that immediately after X25$NWDRIVER 
is loaded an application tells X25$NWDRIVER the numeric
value of the rights identifiers PSI$X25_USER and PSI$DECLNAME.
Thereafter processes wanting to use X.25 should have 
the appropriate numeric rights identifier. 

The other possibility is that the X.25 security may be configured
such that PSI$X25_USER is insufficient to allow X.25 calls
to the selected DTE and DTE address.