| 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 |
hello, A field engineer here experienced the following : Customer is running vws 4.2 and vms 5.2. he recently installed vwsdecw010. What happens : - constantly a login is made via terminal wsa1:, detached processes are created almost every second. This cannot be stopped. customer suspends jobcontroller to stop this - decwindow window only remains a second on top of the vws window (as it should remain) after reboot. After that it disappears. - executing decw$startup a second time generates again a series of detached processes, in other words always 2 identical processes are running at the same time loginout.exe - after reboot same problem remains - customer runs startvws in systartup_v5 because of terminal settings of csa0: (??) - vws$emulators is put to "true" to avoid hang-problem (is stop/id=xxx window remains... and process in rwast) Can vws$emulators interrupt, disturb (?) decwindows??? Field service engineer who installed this at two different customers ' experienced twice the same problem. What went wrong. ??? any suggestions ????
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2645.1 | STAR::KLEINSORGE | Fred Kleinsorge, VMS Development | Tue Apr 24 1990 11:48 | 32 | |
There is a bug in the VMS V5.2 VWSDECW image. This information
"should" be known to the telephone support people. I thought that
I had asked that it get down there...
To fix the bug with the server. You must replace the DDX image with
the V5.1 DDX image - which is in the same kit. There should be three
savesets. Saveset B contains the VMS V5.1-specific files. The file
DECW$SERVER_DDX_GV.EXE must be extracted using backup and copied into
SYS$SHARE.
What you are seeing is "normal" from the point of view that what
the DECwindows session manager does is to keep trying to gain access
to the workstation to put up the login screen. The WSA process is
the session manager retrying. Eventually it will give up. You can
try to be quick and kill it as well using STOP/ID. When you start
things up again, you end up with two session managers and a slight
problem.
Also note that you can normally see what went wrong by looking in the
SYS$MANAGER:DECW$*.LOG files. This doesn't always work however.
So:
$ SET DEF SYS$COMMON:[SYSLIB]
$ BACKUP/LOG mydisk:[mykit]VWSDECW010.B/SEL=(DECW$SERVER_DDX_GV.EXE) []
Then try things again. If the problem still persists, then the odds
are there is a SYSGEN deficiency of something. Do a AUTOGEN and make
sure you have a *clean* MODPARAMS.
| |||||
| 2645.2 | STAR::KLEINSORGE | Fred Kleinsorge, VMS Development | Tue Apr 24 1990 11:54 | 13 | |
RE the last couple questions:
- As long as STARTVWS is done, there should be no problem where it's
done. The server will keep trying to start for about 5 minutes
waiting for VWS to finish initializing.
- The "hang" problem is caused by an attempt to prevent a parent
process from going away while there are still channels assigned
to the terminal which it owns the P1 space VWS structures for.
- The vws$emulator structure should have ZERO effect on DECwindows.
| |||||