[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

318.0. "2dba002 problem still alive and well" by HPSTEK::JBATES (John D. Bates) Tue Feb 28 1989 11:02

	Well it's time to revisit old problems again. We had a problem
	being discussed in the original now retired DECWindows
	conference with the now famous 2dba002 error.

	XIO: non-translatable vms error code: 0x2dba002

	The problem only occurs for us when we are running from a large
	machine and displaying on a workstation. The last thing I saw in
	the file was that the problem should go away in a later field
	test release. We are now running the SDC VMS and DECWindows and
	the problem has not gone away. 

	I feel that since the error only occurs while running through
	DECNET this should be a major clue as to what is going on. Could
	it be that if you are outside the DECWindows event loop for a
	certain period of time the server assumes you have gone away and
	exits? Do the client and server periodically send things back
	and forth to make sure they are both still active? 

	Does anyone have any clues or workarounds, things are getting
	bad. Users tend to get REAL upset when they work on something
	for a long time just to have the system throw it away for them.
	The only thing I have found was that increasing the number of
	LRPs helped quite a bit but didn't eliminate the problem. 

					John

T.R	Title	User	Personal Name	Date	Lines
318.1		A6INTR::SOCHA	Out in the Field	`Tue Feb 28 1989 11:52`	7
	We also suffered from this problem, but fixed it by raising the server retry parameter DECW$SERVER_RETRY_MAX (I think). See an earlier Note for a discussion of how to set this. We changed it from its default of 3 seconds to 60 seconds. Kevin
318.2	Here's what the message is. I don't know who might be generating it...	IO::MCCARTNEY	James T. McCartney III - DTN 381-2244 ZK02-2/N24	`Tue Feb 28 1989 16:49`	2
	%SYSTEM-F-IVSECIDCTL, invalid section identification match control
318.3	RTFM?	SHARE::LEMONS	And we thank you for your support.	`Tue Mar 07 1989 11:12`	9
	.1> We also suffered from this problem, but fixed it by raising .1> the server retry parameter DECW$SERVER_RETRY_MAX (I think). Where is this documented? In what logical name table should they be defined? And on which 'end' of the link? Thanks! tl
318.4		A6INTR::SOCHA	Out in the Field	`Tue Mar 07 1989 17:15`	5
	The DECwindows parameters DECW$SERVER_RETRY_WRITE_MAX and _MIN are described in Topic 197 of this conference. Kevin
318.5	It happens locally also	HAYAMA::FENNELL	Tim Fennell - HPS CAD	`Mon Aug 21 1989 16:19`	14
	I am gettng this timeout problem when I run locally. I am running VMS 5.1 and DECWindows 051 on a 3500. The problem usually happens when I am debugging code that draws many boxes using XFillRectangles. If I break in the loop that draw these boxes I am nearly guaranteed to get a timeout error. I have synchronize turned on, if that is any help. It seems to be confined to interactions with the debugger, as I have played with other windows, with no ill effect. I tried changing the timeout from 3 to 60 seconds which was discussed previously, and that had no effect. Tim