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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1972.0. "VAX3100 hung while modifying password" by ZPOV01::JOHNSEAH () Wed Dec 27 1989 03:58

    
    Hi,
    
    My customer has a VAX3100 running DECwindow, he experiences the
    following problem while changing password:
    
    	$ set def sys$system
    	$ run authorize
    	UAF> mod john /pass=XXX
    
    Then the screen blanked ff, windows disappeared, and the message:
    	object name: sys$common:[sysexe]sysuaf.dat;1
    	object type: file
    	user record modified = john
    	field modified: pass
    
    The workstation hung.
    
    This system is installed several months back and was running fine then.
    
    Please advise on what could possible have gone wrong.
    
    
    Rgds
    John
T.RTitleUserPersonal
Name		DateLines
1972.1Due to OPA0:EVTIS2::HOANGWed Dec 27 1989 04:1711
     Hi,
    
    	I think your customer has OPCOM or Security Audit running on
    the system. What happens is VMS is sending a message to the Operator
    console OPA0: which stays at the top 5 lines of the screen.
    	You just have to DO <CTRL><F@> to get rid of OPA0: and DECWINDOWS
    will come back again.
    
    				Hope this help,
    				Dugn HOANG
    				TSC EVRY FRANCE.
1972.2STAR::MFOLEYRebel Without a ClueWed Dec 27 1989 10:005
       
       
       	Control-F2 will fix it.
       
       							mike
1972.3LOWELL::JACKMarty JackWed Dec 27 1989 11:132
    Might also suggest SET TERMINAL/PERMANENT/NOBROADCAST OPA0: sometime
    during startup.
1972.4OPC$OPA0_ENABLECSC32::M_MURRAYWed Dec 27 1989 11:4814
	Chances are excellent that this is a 5.2 system (OPCOM and
	the Audit Server are started by default in VMS 5.2). 5.2
	provides some logicals to control the behavior of OPCOM.
	OPC$OPA0_ENABLE is set to TRUE in SYS$MANAGER:SYLOGICALS.COM.
	Edit SYLOGICALS.COM to make it come up FALSE, which will 
	inhibit OPCOM writing to OPA0.	This is documented in the 
	fine release notes for VMS 5.2, page 3-63. 
	The fine Version 5.2 New Features manual details changes to
	Security Auditing on pages 2-1 throgh 2-3.


Cheers,
Mike