T.R | Title | User | Personal Name | Date | Lines |
---|
3094.1 | Use V5.3-1 with SPX | STAR::ORGOVAN | Vince Orgovan | Fri Jul 20 1990 18:37 | 5 |
| VMS DECwindows support of the SPX option started with VMS V5.3-1.
If you are really running VMS V5.3, you've probably got a field
test version of DECwindows SPX support and should consider upgrading
to V5.3-1. None of the CSC patches are applicable the field test
versions.
|
3094.2 | Pb in 5.3-2 also with ico -dbl | EVTIS1::MALASPINA | I know someone who knows ! | Mon Sep 10 1990 06:25 | 18 |
| Hi !
I have the same kind of problem but I AM RUNNING VMS 5.3-2.
You can reproduce this using the decw$examples ico with double
buffering.
Issue the following command and you'll get the problem :
$ MC DECW$EXAMPLES:ICO -dbl.
The DECW$SERVER process then takes about 75 % CPU time and you then
have trouble with the pointer which does no longer respond "smoothy"
to a gentle move !
Any Ideas. (VS3100 SPX with 24 MEGA's).
Thanks a lot !
|
3094.3 | Me too! | H2SO4::GERSBACH | Edwin Gersbach CS Switzerland | Wed Oct 31 1990 11:22 | 25 |
| I was just logged in on a customers cluster with 6 SPX's when he called me
because one of the stations hung. I've seen the DECW$SERVER_0 process was in COM
state all the time. Using SHOW PROC/CONT I got the following values:
PC 00132688 / 00132690
PSL 03C00009
SP 7FF8E948
Event 60000001
80000000
As I could never see any other PC than the two listed above, I guess it hung in
a very tight loop. It did not do any I/O and the peak virtual size was somewhere
between 14000 and 15000 (VIRTUALPAGECNT was at 150000).
The customer says that he encounters such a hang every other day on one of the
6 stations.
Can anyone get some information from these values? What does the server do or
wait for in this loop?
Thanks in advance
Edwin
P.S.
VMS is V5.3-1
|
3094.4 | Cliplist messages in the log? | VINO::MCARLETON | Reality; what a concept! | Wed Oct 31 1990 11:47 | 8 |
|
Look in the SYS$MANAGER:DECW$SERVER_0_ERROR.LOG file to see if there
are any lines that have the message "Cliplist did not get into
Offscreen". If you do then you have the problem reported in QAR
1650 in the V54-FT database on TRIFID::. You might also want to look
at note 3224.* in this file.
MJC
|
3094.5 | No error in logfile | H2SO4::GERSBACH | Edwin Gersbach CS Switzerland | Thu Nov 08 1990 07:56 | 7 |
| Sorry, I forgot to mention that I already checked the logfiles. Actualy it was
one of the first things I did, but there was nothing in it but the usual
CONNECTION ACCEPTED/CLOSED messages.
Shall I enter another QAR?
Edwin
|
3094.6 | More information needed | STAR::VATNE | Peter Vatne, VMS Development | Thu Nov 08 1990 17:46 | 4 |
| We can't decode the PC without the contents of the server error log.
Go ahead and enter a QAR. However, if this is holding up a customer,
you should really escalate this...
|