[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

3102.0. "no WSAx process at login time" by EWBV04::NAGANO (Yuji Nagano, CSC/Tokyo Support Engineer) Fri Jul 20 1990 02:40

I have a problem that is no WSAx process at login time.
The DECW$SERVER_0 process is in HIB state.
I found the following message in the DECW$SERVER_0_ERROR.LOG.

%DECW-W-ATT-FAIL ,failed to attach transport LOCAL
-SYSTEM-F-PRIVINSTALL ,shareable images must be installed
to run privileged image.

I checked SYS$SHARE:DECW$TRANSPORT_LOCAL.EXE.
This image was installed with "Open","Hdr","Prot","Shar","Lnkbl" attributes.
And the file protection is (RWED,RWED,RWED,RE). 

Is there any other things to be examined ? 


VMS V5.3-1
VS3100 LAVC

Thanks in advance.
		Yuji Nagano CSC/Tokyo Japan

T.R	Title	User	Personal Name	Date	Lines
3102.1		STAR::ORGOVAN	Vince Orgovan	`Fri Jul 20 1990 18:51`	9
	The message "%DECW-W-ATT-FAIL ,failed to attach transport LOCAL" means that the server couldn't connect to the local transport. Without it, loginout will never be able to connect to the server. The install entry for decw$transport_local.exe looks OK. Is decw$transport_common.exe properly installed? Another thing you should check is to make sure you haven't defined a logical name called "local" in your system startup files.
3102.2		EWBV23::NAGANO	Yuji Nagano, CSC/Tokyo Support Engineer	`Mon Jul 23 1990 04:46`	17
	I checked SYS$SHARE:DECW$TRANSPORT_COMMON.EXE. This image was also installed with "Open","Hdr","Prot","Shar","Lnkbl" attributes. The file protection is (RWED,RWED,RWED,RE). The logical name "local" is not defined in the SYSTARTUP_V5.COM and command procedure files called from the SYSTARTUP_V5.COM. The logical name "decw$server_transpots" is defined with "/trans=term" attribute. So it is no problem. I would like to know about the message "%DECW-W-ATT-FAIL" more detail. Does the message mean that the server could not call a routine in the DECW$TRANSPORT_LOCAL.EXE ? Thanks in advance. Yuji Nagano CSC/Tokyo Japan
3102.3	Meaning of DECW-W-ATT_FAIL	STAR::VATNE	Peter Vatne, VMS Development	`Mon Jul 23 1990 15:06`	11
	Many things can cause DECW-W-ATT_FAIL, from being unable to image activate DECW$TRANSPORT_LOCAL.EXE, to not being able to call the initialization routine in the specific transport. In this case, the system status SYSTEM-F-PRIVINSTALL tells me that the ATTACH_TRANSPORT routine was not able to image activate DECW$TRANSPORT_LOCAL.EXE. We must concentrate on why that is so. Since the COMMON and LOCAL images seem to be installed correctly, then I can only draw the conclusion that the transport is not finding the installed images. Some more possibilities to check: is the logical name SYS$SHARE: redefined? Are there extra versions of DECW$TRANSPORT_LOCAL.EXE in either SYS$SPECIFIC:[SYSLIB] or SYS$COMMON:[SYSLIB]?