[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

2776.0. "V5.3-1 DECterm abort problem" by CSC32::D_COHN (Semiprodigious) Wed May 16 1990 18:41

	I am currently at an impasse in trying to figure out what is causing 
the following problem with DECterm and would appreciate any and all input that 
would help shed some light on this...

	Customer is currently running V5.3-1 of VMS in a LAVc environment.  He 
has noticed that since going to V2.0 of DECWindows that he is having 
"intermittant" problems in creating multiple DECterms.  He indicates that he 
will sometimes encounter a problem with the DECterm controller aborting (see 
the ACCOUNTING record below) after the third or fourth DECterm is created.  He 
has seen this problem both locally and remotely.  When he runs DECterm remotely 
he claims that he recieves an ACCVIO with PC=0001A915 and VC=0ACDC88.  In 
"local" mode it bellys-up with a final exit status of "02DBA002" (FATAL I/O 
error?).


	So far we have been unable to capture a process dump (any pointers 
along this line would be helpful).  I have also reviewed his PQL parameters and 
they either meet or exceed the minimums.  He has cleared out his process's 
default files (eg., "DECW$SM_GENERAL.DAT") and this didn't change the behavior. 
Other system resources are in good shape - no pool expansion, no problems with 
working sets and plenty of pagefile quota and space available. 


	Any ideas??

Dennis

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DETACHED Process Termination
----------------------------

Username:          CO                UIC:               [DEVELOP,CO]
Account:           DEVELOP           Finish time:       15-MAY-1990 16:33:34.82
Process ID:        22800082          Start time:        15-MAY-1990 09:01:42.93
Owner ID:                            Elapsed time:                0 07:31:51.89
Terminal name:                       Processor time:              0 00:02:06.45
Remote node addr:                    Priority:          7
Remote node name:                    Privilege <31-00>: 00108000
Remote ID:                           Privilege <63-32>: 00000000
Queue entry:                         Final status code: 02DBA002
Queue name:
Job name:
Final status text: <no text>

Page faults:             3219        Direct IO:                 30
Page fault reads:         384        Buffered IO:               41
Peak working set:        1617        Volumes mounted:            0
Peak page file:          5728        Images executed:            1


T.RTitleUserPersonal
Name
DateLines
2776.1KYOA::KOCHMy brother did not lose the electionWed May 16 1990 23:462
	What is in the SYS$MANAGER:decw$server_%_output.log and
	SYS$MANAGER:decw$server_%_error.log files?
2776.2Back to you...CSC32::D_COHNSemiprodigiousThu May 17 1990 17:13174
>   <<< Note 2776.1 by KYOA::KOCH "My brother did not lose the election" >>>
>
>	What is in the SYS$MANAGER:decw$server_%_output.log and
>	SYS$MANAGER:decw$server_%_error.log files?

	There was nothing in the DECW$SERVER_0_OUTPUT.LOG file but here
here is the contents o0f the DECW$SERVER_0_ERROR.LOG:

*(Please look at the other information posted at the end of this file...)*

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15-MAY-1990 19:54:31.2 Hello, this is the X server
Dixmain address=13074
Now attach all known txport images
%DECW-I-ATTACHED, transport DECNET attached to its network
%DECW-W-ATT_FAIL, failed to attach transport LAT
-SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image
in SetFontPath
Connection 99700 is accepted by Txport
out SetFontPath
GPX color/monochrome support loaded
gpx$InitOutput address=13a410
Connection Prefix: len == 42
15-MAY-1990 19:56:02.6 Now I call scheduler/dispatcher
15-MAY-1990 19:56:03.4 Connection 99738 is accepted by Txport
15-MAY-1990 19:56:08.0 Connection 99700 is closed by Txport
16-MAY-1990 08:46:53.8 Connection 99738 is closed by Txport
16-MAY-1990 08:46:55.9 Connection 99700 is accepted by Txport
16-MAY-1990 08:47:04.5 Connection 99770 is accepted by Txport
16-MAY-1990 08:48:03.0 Connection 99738 is accepted by Txport
16-MAY-1990 08:48:03.4 Connection 9adf8 is accepted by Txport
16-MAY-1990 08:48:10.2 Connection 9ae30 is accepted by Txport
16-MAY-1990 08:48:11.8 Connection 9ae68 is accepted by Txport
16-MAY-1990 09:12:15.4 Using extra todo packet pool...
16-MAY-1990 11:32:57.3 Connection 9ae68 is closed by Txport
16-MAY-1990 11:34:04.7 Connection 23e230 is accepted by Txport
16-MAY-1990 11:39:38.1 Connection 23e230 is closed by Txport
16-MAY-1990 11:43:22.7 Connection 23e230 is accepted by Txport
16-MAY-1990 11:51:27.5 Connection 9ae30 is closed by Txport
16-MAY-1990 11:52:04.9 Connection 23e268 is accepted by Txport
16-MAY-1990 12:06:03.0 Connection 23e230 is closed by Txport
16-MAY-1990 12:06:40.2 Connection 23e230 is accepted by Txport
16-MAY-1990 12:10:51.4 Connection 23e230 is closed by Txport
16-MAY-1990 12:11:16.4 Connection 23e230 is accepted by Txport
16-MAY-1990 13:23:12.9 Connection 23e230 is closed by Txport
16-MAY-1990 13:23:52.2 Connection 23e230 is accepted by Txport
16-MAY-1990 13:28:08.2 Connection 23e6a0 is accepted by Txport
16-MAY-1990 13:34:41.8 Connection 2bf600 is accepted by Txport
16-MAY-1990 13:34:42.8 Connection 2bf600 is closed by Txport
16-MAY-1990 13:38:12.4 Connection 2c3a30 is accepted by Txport
16-MAY-1990 13:38:19.1 Connection 2c3a30 is closed by Txport
16-MAY-1990 13:52:19.5 Connection 2c3a30 is accepted by Txport
16-MAY-1990 13:52:21.3 Connection 2c3a30 is closed by Txport
16-MAY-1990 14:13:36.0 Connection 9adf8 is closed by Txport
16-MAY-1990 14:13:36.6 Connection 99738 is closed by Txport
16-MAY-1990 14:13:37.0 Connection 23e230 is closed by Txport
16-MAY-1990 14:13:37.6 Connection 23e268 is closed by Txport
16-MAY-1990 14:13:38.4 Connection 23e6a0 is closed by Txport
16-MAY-1990 14:13:46.9 Client 3 resets the server
 16-MAY-1990 14:13:51.6 GPX color/monochrome support loaded
gpx$InitOutput address=13a410
Connection 309a48 is accepted by Txport
16-MAY-1990 14:13:54.9 Now I call scheduler/dispatcher
16-MAY-1990 14:13:55.4 Connection 307018 is accepted by Txport
16-MAY-1990 14:13:59.9 Connection 309a48 is closed by Txport
16-MAY-1990 14:14:16.7 Connection 307018 is closed by Txport
16-MAY-1990 14:14:21.6 Connection 307050 is accepted by Txport
16-MAY-1990 14:14:25.7 Connection 307088 is accepted by Txport
16-MAY-1990 14:15:05.6 Connection 307018 is accepted by Txport
16-MAY-1990 14:15:21.0 Connection 307018 is closed by Txport
16-MAY-1990 14:16:05.6 Connection 307018 is accepted by Txport
16-MAY-1990 14:28:33.0 Connection 307018 is closed by Txport
16-MAY-1990 14:29:02.0 Connection 307018 is accepted by Txport
16-MAY-1990 14:30:50.4 Connection 314530 is accepted by Txport
16-MAY-1990 14:32:54.8 Connection 3070c0 is accepted by Txport
16-MAY-1990 14:33:56.1 Connection 3070f8 is accepted by Txport
16-MAY-1990 14:33:57.5 Connection 307130 is accepted by Txport
16-MAY-1990 15:40:51.7 MEMMGR/XREALLOC - zero amount is requested
16-MAY-1990 15:40:52.5 MEMMGR/XREALLOC - zero amount is requested
16-MAY-1990 15:40:52.9 MEMMGR/XREALLOC - zero amount is requested
16-MAY-1990 16:02:40.8 Connection 3070c0 is closed by Txport
16-MAY-1990 16:03:30.5 Connection 3070c0 is accepted by Txport
16-MAY-1990 16:18:14.2 Connection 307168 is accepted by Txport
16-MAY-1990 16:18:15.3 Invalid access from transport: DECNET         
                                                node: HERMES         
                                                user: KAM            
16-MAY-1990 16:18:38.2 Connection 307168 is accepted by Txport
16-MAY-1990 16:18:38.7 Invalid access from transport: DECNET         
                                                node: HERMES         
                                                user: KAM            
16-MAY-1990 16:18:54.3 Connection 307168 is accepted by Txport
16-MAY-1990 16:18:54.7 Invalid access from transport: DECNET         
                                                node: HERMES         
                                                user: KAM            
16-MAY-1990 16:18:58.3 Connection 307168 is accepted by Txport
16-MAY-1990 16:18:58.6 Invalid access from transport: DECNET         
                                                node: HERMES         
                                                user: KAM            
16-MAY-1990 16:20:11.7 Connection 307168 is accepted by Txport
16-MAY-1990 16:21:04.9 Connection 3071a0 is accepted by Txport
16-MAY-1990 16:21:05.3 Connection 3071a0 is closed by Txport (status = 20e4)
16-MAY-1990 16:23:50.6 Connection 3071a0 is accepted by Txport
16-MAY-1990 16:23:58.9 Connection 3071a0 is closed by Txport
16-MAY-1990 16:24:19.5 Connection 3071a0 is accepted by Txport
16-MAY-1990 16:24:26.7 Connection 3071a0 is closed by Txport
16-MAY-1990 17:09:20.8 Connection 3071a0 is accepted by Txport
16-MAY-1990 17:58:09.2 Connection 3071a0 is closed by Txport
16-MAY-1990 17:58:10.1 Txport status = 2dba002 ( copy and write) on client 9
16-MAY-1990 18:03:28.4 Connection 3071a0 is accepted by Txport
16-MAY-1990 18:04:10.3 Connection 3071d8 is accepted by Txport
16-MAY-1990 18:04:10.8 Connection 3071d8 is closed by Txport (status = 20e4)
16-MAY-1990 18:06:49.9 Connection 3071a0 is closed by Txport (status = 20e4)
16-MAY-1990 20:12:45.4 Connection 307168 is closed by Txport (status = 20e4)
17-MAY-1990 09:34:07.4 Connection 314530 is closed by Txport
17-MAY-1990 09:40:11.0 Connection 307168 is accepted by Txport
17-MAY-1990 10:10:03.7 Connection 307130 is closed by Txport
17-MAY-1990 10:10:05.0 Connection 3070f8 is closed by Txport
17-MAY-1990 10:10:05.4 Connection 3070c0 is closed by Txport
17-MAY-1990 10:10:05.6 Connection 307018 is closed by Txport
17-MAY-1990 10:10:06.0 Connection 307168 is closed by Txport
17-MAY-1990 10:10:21.6 Client 3 resets the server
 17-MAY-1990 10:10:27.9 GPX color/monochrome support loaded
gpx$InitOutput address=13a410
Connection 309c68 is accepted by Txport
17-MAY-1990 10:10:31.6 Now I call scheduler/dispatcher
17-MAY-1990 10:10:32.0 Connection 307018 is accepted by Txport
17-MAY-1990 10:10:37.6 Connection 309c68 is closed by Txport
17-MAY-1990 10:10:58.3 Connection 307018 is closed by Txport
17-MAY-1990 10:11:01.0 Connection 307050 is accepted by Txport
17-MAY-1990 10:11:11.4 Connection 307088 is accepted by Txport
17-MAY-1990 10:12:08.6 Connection 307018 is accepted by Txport
17-MAY-1990 10:12:14.9 Connection 3070c0 is accepted by Txport
17-MAY-1990 10:12:16.4 Connection 3070f8 is accepted by Txport
17-MAY-1990 10:13:35.2 Connection 314b80 is accepted by Txport

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTE: 	This is the output from a "interactive" startup of DECterm from the 
	FILEVUE "DCL Command" window on the WorkStation that is having these
	problems:

WOOKIE$ set proc/dump
WOOKIE$ mcr decw$terminal

DECterm version V2.0 now at your service...

To create DECterms, use the Session Manager or call the
DECwTermPort() routine from another process.
X Toolkit Warning: Drm__CW_FixupCallback: Callback routine 'angle_angle_cb' not
registered - DRMNotFound
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000004, PC
=001126FD, PSL=03C00004

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                7FE513FC
        Name   = 0000000C                00000000
                 00000000                20000000
                 00000004                7FE513FC
                 001126FD                7FE513E0
                 03C00004                000CC7CC
                                         00000002
                                         00000000
                                         000A29A0
                                         00186E1C

        Register dump

        R0 = 00000001  R1 = 00000000  R2 = 00000AF4  R3 = 00000000
        R4 = 000A06A8  R5 = 00000000  R6 = 00000000  R7 = 00000002
        R8 = 7FE514A4  R9 = 000B34D4  R10= 001DD722  R11= 00000000
        AP = 7FE51370  FP = 7FE51330  SP = 7FE513AC  PC = 001126FD
        PSL= 03C00004
2776.3HANNAH::MESSENGERBob MessengerThu May 17 1990 18:1221
Re: .2

>DECterm version V2.0 now at your service...
>
>To create DECterms, use the Session Manager or call the
>DECwTermPort() routine from another process.
>X Toolkit Warning: Drm__CW_FixupCallback: Callback routine 'angle_angle_cb' not
>registered - DRMNotFound
>%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000004, PC
>=001126FD, PSL=03C00004

That's interesting.  I'm not sure why 'angle_angle_cb' was not registered; it
should have been.  Maybe the DECterm controller ran out of memory or some
other resource; that can make it crash in strange ways.  Try increasing your
PQL_DPGFLQUOTA parameter in SYSGEN.

Another possibility is that there's something wrong with your DECW$TERMINAL.UID
file, but this seems less likely because 'angle_angle_cb' should have been a
valid callback routine.

				-- Bob
2776.4We checked that one...CSC32::D_COHNSemiprodigiousFri May 18 1990 13:259
re: .3

	The current PQL_DPGFLQUO is set at "25000"...  I spent lots of time 
reviewing process/system resource allocation and usage and at this point I am 
at loss as to which, if any, would be the culprit.  

	Any other suggestions??

Dennis
2776.5HANNAH::MESSENGERBob MessengerFri May 18 1990 17:186
Re: .4

You might try replacing DECW$SYSTEM_DEFAULTS:DECW$TERMINAL.UID with a copy
from a working system.

				-- Bob
2776.6More problems with 0.EIGER::STACHERMon May 21 1990 06:2213
What is the solution to problem 0?

VMS 5.3-1

My customer has an LAVC with VS 3100, and VS2000 as satellite. He can login via 
DECwindow, but if he creates a DECterm or starts the FileView, DECwindow Session
Manager will hang. Same problems with all satellites.

I tryied out encreasing PQL_DPGFLQUOTA. Nothing changed, same problems.
I've checked also DECW$TERMINAL.UID file, but date and size are the same as on
VMS V5.3. And with VMS V5.3 there are no problems.

Any Ideas?
2776.7Are they reading from the terminal in LOGIN.COM?HANNAH::MESSENGERBob MessengerMon May 21 1990 11:2914
Re: .6

Have your customer check their LOGIN.COM and SYLOGIN.COM files and make sure
they aren't doing an INQUIRE, SET TERMINAL/INQUIRE or anything else that
reads from the terminal.  If they are reading from the terminal they should
make the read condiutional, e.g.

	$ IF .NOT. F$GETDVI("SYS$OUTPUT:", "TRM") THEN GOTO NOINQUIRE
	$ SET TERMINAL/INQUIRE
	$ NOINQUIRE:

This has been discussed in several other notes.

				-- Bob
2776.8Suddenly workingEIGER::STACHERWed May 23 1990 04:3912
SYSLOGIN,COM and LOGIN.COM are OK.

Thank's for the hint.

Suddenly, all satellites are working and I don't known exactly way. It's a
strange thing.

In a view days my customer will reboot the whole LAVC and then we'll see what
happen.

Cheers
Christian